PO wrong in /SAPPO/PPO2. Purchase req. xxxxxxxxxxxx: follow-on document from external system not allowed

[Former Member]

Hi experts,

We have got a problem when we try to create a PO in ECC system from SRM System. the PO is wrong in transaction /SAPPO/PPO2 in ECC. the error is the follow:

"Purchase req. xxxxxxxxxxxx: follow-on document from external system not allowed"

Our scenario is:

1.  A Purchase Request is created in ECC system and is transfered to SRM as a SC.

2. The SC is send to SOCO to determination supply source

3. The RFX is created

4. the bid is accepted and the PO is create in ECC systen from SRM

The problem is In the last step because the PO is wrong in  /SAPPO/PPO2.

Can anyone help me?

Thanks by advance.

Best regards,

Mar

[Former Member · Accepted solution]

Hi,

The no error is MEPO303

Thanks

Best regards,

Mar

[ivy_li · Accepted solution]

Hi Mar,

The error itself is too general.

First I suggest you check the outbound and inbound XML messages in SRM and ECC system, and check which one is not successfully. If the inbound XML failed, then this should be handled by MM experts.

In order to find out the real error, you have to debug the failed XML with trx sproxy.

Best regards,

Ivy

[Former Member · Accepted solution]

Hi Ivi,

The sender is SRM and de receiver is ECC system. I can see the menssage is in Tx /sappo/sappo2 in ECC system.  And thanks we have been trying to debug the XML by SPROXY but until now we cant see nothing that is the reason for I open this chat.

Best regards,

Mar

[Former Member · Accepted solution]

1753169 - PO not created from bidding engine

Please apply this note in ECC system

symptom

You create a PR in the ECC backend system and send it to the SRM bidding engine. In SRM, a PO is

created from the PR and replicated to ECC. The replication fails with the error message mepo 301:

Purchase requisition is in external sourcing.

Muthu

[Former Member · Accepted solution]

Hi,

I´ve reviewed the level of this SP and We have a lower level than the note recommend so We'll try to apply this note.

Thanks by advance.

Best regards,

Mar

[Former Member · Accepted solution]

Hi Muthutraman,

We have implemented this note and the problem has been solved (the PO has been created in ECC sytem) but the original  PR continue with wrong status (pending to send to external system in the Label "external sourcing") when we see it in ME53N. Could you have any sugestion to solve this problem?

Thanks by advance.

Best regards,

Mar

[alejandro_jimenez2]

hi, please check this thread.

i hope this link could help you to resolved your problem.

regards.

[Former Member]

Hi Alejandro,

I have reviewed the values in this table for the PR and I think that has the right status, don't you?:

(PROC STATUS)-> "E" External Sourcing Value

(EXT PROC STATUS)-> "1"  transferred to the external system, in treatment"

should I review the message XML also to search in any of the tabs some similar value?

Thanks by advance.

Best regards,

Mar

[Former Member]

Hi Maria

I am not sure if you came right with this.The Processing state should be  'E' and the External Status should be "2" - then the requisition will shows accepted. If External status is 1 it will be in pending and no PO can be created.

We wrote ourselves a program to change the status to accepted manually if we want. This is not advisable.

The way you should go about resolving this is looking for the XML that updates the requisition with accepted. It has probably failed somewhere along the line. Look at what time the SC was created in SRM and then look in ECC using transaction SXMB_MONI. You will then be able to find the failed XML and the reason why it failed.

Alternatively you should be able to use /SAPPO/PPO2 and just change your search criteria to look for requisition updates to see the failed update and reprocess the original XML to update the status of the requisition.

Last case scenario use program RESET_STATUS_EXTERNAL_SOURCING and reset the external tab (note it removes it), you will then be able to reprocess the failed PO create using /SAPPO/PPO2.

I found most often the reason the external tab did not update was because a user had the requisition open in me52n. So the error shown, says someone is already processing the requisition.

I hope this helps.

Regards

Wesley

[Former Member]

Hi Maria

Can you check the below settings :

The status of PReq should be "Send to external sourcing Accepted" otherwise system will not allow follow on to be created from SRM.

Incase the status is not Accepted because incoming XML failed, reason could be XML is trying to update the PReq & you might have version management active, release date as mandatory. Incoming XML doesnt have this information & hence fails

Chang the PR setting for 'Release Date' in ECC

[Former Member]

I Vinita,

The PR is still with the status waiting for sending to external system because the XML message is still wrong. In the xml I dont see the version in any tab so I supose it is not mandatory in it. and in ECC system in the settings of PR the flag it is not active.the only that are marked are  0 version and external version. Any suggestion?

thanks

Best regards,

Mar