Unable to transfer Purchase Requisition from ECC to EBP

[Former Member]

Dear Friends.

We are unable to transfer PR from ECC to EBP. System issue stop message in SLG1 transaction for object BBP_EXTREQ

Stop Message Type: Document type for determined backend system is missing.

Warning Message Type: Grant 1111 does not exist.

As per configuration guide we have performed following setting in EBP client

1. We have created organization unit “Entry Channel” under company code.

2. Under Entry Channel we create Local Purchasing Organization.

3. Under Loc Purchasing Org we created Local Purchasing Group with

- attribute BUK as backend company code

- attribute BSA as backend PR type (NB)

- this group is responsible for Entry channel procurement (setting in Function tab)

4. Under Loc Purchasing Group we assigned RFC user which is same defined as RFC user in both EBP and ECC client.

- attribute DP_PROC_TY defined as backend ECC PO type (NB)

5. Attribute CUR define for entry Channel.

6. Remote connection established with the same user defined under Organization Unit

7. Remote user has profile sap_all and sap_new authorization.

8. Material group, Material Type and Vendors are replicated from backend system.

9. Sourcing always allowed is set for all product categories in “Define sourcing for Product Category”.

10. Extended Classic Scenario is active.

11. Defined Tolerance check and assigned TOG attribute.

Performed following setting in ECC client.

12. Defined RFC connection and user same as defined in Organization unit.

13. Defined profile which reference to EBP logical system

14. Maintained table V_T160EX with Material group/Pur group/ Profile combination.

Finally transfer Purchase Requisition from ECC to EBP via report BBP_EXTREQ_TRANSFER. Further the outbound Queue fails with status ANORETRY. Also the log displayed the error ‘Application aborted due to serious problems’

SLG1 in EBP issues stop message “Document type for determined backend system missing” and warning message “Grant 1111 does not exist”.

Any idea what could be the reason?

Please help!!

Sandeep

[Former Member]

Old Messaged closed

[Former Member]

Hey Sandeep,

For transfering PR from backend to SRM in PDP scenario you need two main entries:-

1. AttribureDP_PROC_TY : ECDP is a must.

2. Channel for PDP to be assigned as responsibility to the PRG group."

Please let me know if your problem is resolved by this solution and reward suitable points.

Thanks and Regards

Kapil

[Former Member]

Kapil,

Thanks for your input.

Yes your right attribute DP_PROC_TY is required to create Purchase Order in backend.

When I assign DP_PROC_TY value as the PO document type define in the backend system. System displays these document types as options "Transaction Type for Purchase Order" in Bid Invitation header data and further creates PO in backend based on the document type selected in “Transaction Type for Purchase Order”.

However sometime system behaves really strange there are two attributes DP_PROC_TY and BSA. If we define BSA attribute then DP_PROC_TY attributes are blanked automatically and if we define DP_PROC_TY attribute then BSA attribute is blanked automatically.

Is it that, at any given time only one of the above attribute can be defined in organization structure?

The current situation is, we are able to create follow-on PO document in backend system from Bid Invitation only if the bid invitation is created manually in SRM.

But if we import the Purchase requisition from backend R/3 and then via sourcing we create bid invitation and then try to create PO in backend. System issues following error messages

1. Purchase Order has not been created

2. Number range PO does not exist.

I tried the above scenario with ECPO and ECDP in DP_PROC_TY as well as BSA attribute, but with same results.

If the same user creates a fresh bid invitation in SRM then system creates PO successfully in backend.

Any Idea what could be the reason?

Regards,

Sandeep

[Former Member]

Hi

It seems there is some problem with the Configuaration settings in SRM as well as R/3 side.

<u>Anyways, please have a look at the following links, which might help.</u>

<b>Direct Procurement</b>

http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm

<b>Prerequisites for External Requirements</b>

http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm

<b>Attributes for the SRM Scenario</b>

http://help.sap.com/saphelp_srm50/helpdata/en/84/a7e3389870c05ce10000000a114084/frameset.htm

<b>Direct Material Scenario: Other Planned External Requirements</b>

http://help.sap.com/saphelp_srm50/helpdata/en/6a/4b9e3b891da20ee10000000a114084/frameset.htm

<b>Number range settings</b>

http://help.sap.com/saphelp_srm50/helpdata/en/5d/fd7d3cb7f58910e10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm

<b>Define Transaction types</b>

http://help.sap.com/saphelp_srm50/helpdata/en/10/fd7d3cb7f58910e10000000a114084/frameset.htm

<b>Direct Material Scenario with Planning in SAP APO</b>

http://help.sap.com/saphelp_srm50/helpdata/en/d3/4b9c3b122efc6ee10000000a114084/frameset.htm

Hope this will help.

Regards

- Atul

[Former Member]

Hi Sandeep,

Firstly, Your are Implementing the Extended classic scenario, with the PO created in SRM & later transferred to R/3... for the PDP-PM process.

Please check the attributes in the SRM org plan once again:

1)BSA -- must be the ECPO or any other PO document type you would like to create in SRM.

2)DP_PROD_TYPE---must be the PO document type from the above to create a PO for the PR coming for the R/3.

3)The PO number ranges must be correctly mapped SRM(internal) and R/3 (External) for the above PO document types....

Do carry out the above checks and do go thro the PDP-PM cycle again....come back.

Regards,

RK.

[Former Member]

Thanks RK,

We are able to create PO as follow-on document in SRM for Direct Material and for consumable material we are able to create PO in backend system.

Is there any limitation for direct material that the follow-on document can only be created in SRM and not in backend system?

Regards,

Sandeep

[Former Member]

Hi Kapil,

I am also getting same problem as " Error in the backend communication".

After implementating sap note: 1358973, problem is resolved.

But before implementating SAP note, we can able to replicate PR's which are created with and w/o account assignment.

But after implementing SAP note, only PR's which are created with account assignmnet are replicating into the SRM system.

PR's which are created with out account assignment are not replicating into the SRM system.

Error: MESSAGE : Ext. requirement cannot be created, see application log for object BBP_EXTREQ in the outbound queue.

Can you help me, how to resolve this one?

Thanks & Regartds

Ravi kumar

[Former Member]

Hi,

you can check SLG1 in the target SRM system, object BBP_EXTREQ for the error encountered. Please also check PPOMA settings for the user who created PR and corresponding customization in your workflow.

KR,

Mike

[Former Member]

Hi,

Thanks

Problem was resolved.

Regards

KTK

[Former Member]

Hi Sandeep,

You need to maintain In the attribute DP_PROC_TY ,must be defined as the PO in SRM document type (like EX: ECPO) but not as backend ECC PO type (NB).

This is for the system to understand that the follow on document for the PO to be created in SRM will be of the ECPO.....

Second message

Warning message:" Grant 1111 does not exist"

check your R/3 settings, whether any cost object is Grant is activated or Check whether T-code :GMGRANT is activated in R/3.

Regards,

RK.

Note: Reward points.

[Former Member]

Thanks RK,

We did manage to remove the first error of document type. For the second message we check transaction GMGRANT in R/3, we found Grant Dimension is not active.

Good thing is we tried to transfer PR without account assignment and it worked.

The issue is with account assignment only. Further we analyzed to find that for PR with account assignment is assigning commitment item as 1111.

Which EBP was trying to locate?

In R/3 Fund management is active for which Commitment item is required.

So from EBP point of view do we need to configure something for fund management?

We following attribute in organization configuration

Commitment Item

Fund

Fund Center

Grant

I tried to with assigning the commitment item to the attribute but it gave the same error.

Do we need to configure something in EBP for Fund Management, if it’s activated in R/3?

Regards,

Sandeep Parab

[Former Member]

Hi Sandeep,

Since the issue is with the account assignment and cost centre.

In R/3, KS02(cost centre), get to the control tab, and <b>uncheck</b> the COMMINTTMENT field and run thro the cycle...

This might help you...

Regards,

RK.

[Former Member]

Thanks for your update RK,

We checked Cost Center maintenance and found the Commitment field unchecked.

Anyway I think this could be because of partial configuration of Fund Management setting in R/3 client. So we shall first get it fully configured by FI in R/3 and then try to push PR.

Anyway thanks for your help.

Sandeep