Limit Order & SAP note 1355894

[Former Member]

Hi,

We are running SRM 550 at SP13, SAP have released a note 1355894 in SP16 that seems to imply that the category type for a Limit order should be B = Limit not D = Service. That seems logical?

Our current system configuration enters an S, and although in general this works OK, we do occasionally have an issue when a user tries to reverse a limit order confirmation in SRM. The system will not allow it because a service entry sheet has been generated for the back end PO.

As we have not activated the service part of SRM, our users do not have access to reverse the service entry sheet and so this function must be carried out by a BPO or CCC team member with full access.

Does everyone end up with an S for a Limit Order item category type in their back end system?

If you have this, what problems do you get.?

Can anyone who has implemented the note 1355894 in an SRM 550 system let me know what the effect was?

Thanks in advance

Allen Brooks

SRM BPO

Sunderland City Council

[Former Member]

Thanks again question ios answered

[Former Member]

Muthu,

Thanks for your reply.

If I am understanding you correctly, this note only works where a supplier has No Confirmation Expected entered against the master record.

The note is not very clear on this point and then the question remains, why do we need to use S for one entry and B for another?

As we always expect confirmations for all our PO's it would appear that the note may have no effect on our systems so rather than applying the note in advance we will wait until we get to the SP16 application in the year ????.

Thanks for the info this question is now answered.

Regards

Allen Brooks

SRM BPO

Sunderland City Council

[former_member183819]

Hello Allen

if it is a service , we would get D

for eg item category B , we can not do good receipt in backend.Only direct INVOICE

br

muthu

[former_member183819]

Hello Allen

SAP Note 1355894 - Limit item becomes Service Item . This Note is a right note since it mishaves in ECC system . it was spposed to create item category B but it created item category B.

SInce User enter only invoice not Confirmation button.

obviously system should create B rather than D since NO CONFIRMATION REQUIRED.

IT is because of ECC vendor masterdata causess problem in the replicated POs. ie Prerequisite - in the relevant vendor master data, the "confirmation

expected" indicator is set.

br

muthu