cancel
Showing results for 
Search instead for 
Did you mean: 

Central Contract Backend document number is not come back

Former Member
0 Kudos

Hi, all~

Pls pay attention this issue.

I saw similiar question but not answered.

We implemented SRM 7.

After Central Contract create, Contract number is transfered to ECC but didn't back.

In tracking tab, there are no backend number.

And I think this is related with XI.

when i check sxmb_moni, 'PurchasingContractSRMReplicationConfirmation_In' message status is not Grand Prix flag.

(Status is 'Transfer to External Applcation', not 'Process Successfully')

What is solution?

Best regards,

SKY.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

Status "Transfer to External Application" indicates that Contract in question has application related errors (UOM, Product, etc)

To understnd the error, go to txn /SAPPO/PPO2. Here search for your document and you will get the errors.

You can correct the document/XML and reprocess the XML message.

Thanks,

Sushil.

Former Member
0 Kudos

Hi~ sushil...

Thanks for answer.

I already check /SAPPO/PPO2.

The error message is 'The attributes of the user are inconsistent or not defined. See transaction PPOMA_BBP.'.

But there are no inconsistency or undefined attribute.

We checked it through 'PPOMA_BBP' and 'BBP_CHECK_USERS'.

Could you recommand other way to find out exact point(attribute) about error message?

Former Member
0 Kudos

Please check below config:

Have you maintained XI communication user in org structure?

Assign roles /SAPSRM/ST_PURCHASER to XI user

Check if service calls maintained for central contract confirmation_Out from backend to SRM. Check OSS note 1268821 for service call setup in XI.

Thanks,

Jagadish