BBP_EXTREQ_TRANSFER - Error ANORETRY

[Former Member]

Hello SRM Experts,

we are working on a SRM 6.0 classic scenario system. We move the PRs from R/3 4.6C backend to the SRM system via the report "BBP_EXTREQ_TRANSFER". No problem at all. The external requirement SC is created and afterward the PO is create through SoCo. If the PR requester changes the delivery date for one PR that have been lifted to SRM and there is an PO created the outbound queue in SMQ1 get stuck with the status ANORETRY and no message error shows up in SLG1.

Has anybody have this issue?

Thank you very much for your answers.

Kind regards

Célio Medeiros

[former_member183819]

SAP advised as suggeted by Virender.

Note 1247922 - Change of External Requirement sends requirement to SOCO

Symptom

When an external requirement is getting changed in the backend system, the corresponding shopping cart item is sent back to the 'Sourcing Cockpit', the reason is that the Purchaser should be informed about this change (for example a delivery date or quantity), and according to this change, the Purchaser will react directly in the PO.

But when REQUESTER edit the PM Order in IW32 would have warned him that PO has been already created.

however

Consulting note.

Some Customers do not want to have such functionality, that for every change in the external requirement, the system will send the corresponding shopping cart item to the Sourcing Cockpit.

After applying this note, the corresponding shopping cart item is sent back to the sourcing cockpit, only in case the quantity in the external requitrement is increased.

See the piece of above advise if the quantity changes(

initially PM order ordered 2 qty and PO created 2 qty and again PM person edited 5 qty in PM order and SC qty 3 will be shown in the cockpit anfd BUYER can source for remaining 3 qty only.

my understanding for changing delivery date in the PM ORder afer PO created ,the entry should not happen in the EPRSTRANS table again.

OPEN THE QUEUE and see any piece of data inside ? As per SAP standard delivery date will not update in SC and PO as you expected if PM person change the delivery dat elater Po created.

[Former Member]

Hi Muthuranam,

Thank you for the OSS note.

We're currently facing a related problem which is when a PM order is re-openned and subsequently closed, the system updates the PReq Release date. This then triggers the send to the SRM system and in most cases queue blockage.

Thanks,

Jerry

[former_member183819]

Hi

Note 1168110 - External requirement transfer fails when PM order changed

You have transferred a purchase requisition to the SRM system, which is created out of a work order. Change the work order so that the purchase requisition is also changed. However, the changed purchase requisition is not transferred to the SRM system.

The application log in the SRM system shows the error message "Enter exactly one partner of type Requestor"

Other terms

BBP_EXTREQ_TRANSFER IW32 BBP_PD428

Reason and Prerequisites

Program Error. The issue solved partially with the note 1038484. But, if purchase requisition have more than 5 items, system fails to transfer due the error "Enter exactly one partner of type Requestor"

Solution

Import the corresponding support package to correct this error. To correct this error in advance, implement the attached correction instructions.

-- but this note is for Sp16

you need tell step by step process

PM process and Procurement process step by step ..

are the below steps followed

Step 1 : -like PM Order creatre d / rleased -PR created and Approved -SC - PO Created - GR done

Step 2:- PM Order settled PM Order Closed

Step 3:- PM Order reopened ..and changed some data

Step 4:- the same PR awaiting approval and approved ..

step 5:- Queue strucked?

[Former Member]

Hi Virender.

In fact, it is work order Purchase requistion (PM). When the PM guy change dates in the work order the delivery date in PR is changed automaticaly. This trigger the PR to the EPRTRANS and when the program BBP_EXTREQ_TRANSFER runs, the queue in SMQ1 get stuck with the status ANORETRY.

Regards

Célio Medeiros

[Former Member]

Celio

Once a PR is pushed to SRM , you are not supposed to push it again for the changes to be updaed in SRM SC.

Make the changes in the SC and PR(in ECC) manually....if required

Regards

Virender Singh