SRM PR is not getting created in ECC backend

[Former Member]

Hello Experts,

We are running SRM 7.0 with SRM-MDM Catalog, we are using SRM for shopping. We do have PI 7.11 running in the Environment as well.

We are on ECC 6.0 with Ehp 4.0

Purchase Order:

However we can see the PO creating successfully using PI.

Question, in the SRM table (BBP_FUNCTION_MAP), we see the object type: BUS2012 for ERP 4.0 has adapter name: /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP for when creating PO. Please see teh screen shot.

is this the reason that we need PI?

Purchase Requisition:

PR Creation is not working:

PR is not getting created in the ERP, PR uses Object type: BUS2105, Adpater CL_BBP_BS_ADAPTER_RQ_CRT_470 for ERP 4.0 System type, can you please tell me if the adapter is correct for ERP 4.0 system type?

I also have a question to ask:

1) Where did you see that PR/PO was send to PI System (PI1)? My understanding is that since ERP amd SRM are 2 ABAP Systems, why we cannot send the PR/PO directly to ERP system from SRM? Why do we need a middleware(PI) in between for this process? We should be able to USE BAPI function to do it correct?

Please advice.

Thanks

Kumar

[former_member183819]

Hi

please expalin more

- Create a sc from catalog- PO created since it treated as fixed vendor -partner function 19- PO created

- create a sc (describe procurement ) and assign prefered vendor - partner function 39 and no sourcing configured - PR created if it it classic or PO held created if you are in ECS if no sourcing config done.

- create a sc (describe requirement) and assign valid fixed source of supply - contract = partner function 19.- PO created in both scenario

so you need to expalin here what technical scenario in SRM ?

Do you want to create a PR in the backend rather than PO

in SRM determines number range for all SC follow on docuemnts like PR and PO.

PR and PO decision upon your data in the shopping cart and Technical scenario . so expalin more what is your expectations.

for more understanding visit this node

Define Objects in Backend System (Purch. Reqs, Reservations

Muthu

[Former Member]

Hi Muthu,

Thanks for the details,

We are using Classic Scenario, the business scenario we have adopted is:

when SC is created without vendor details (described as text requirement), a PR should be created in the Back end system.

When SC is created with Vendor details (Contract, Purchase Info record), a PO should be created in the Back end system.

We have defined number ranges and document types for both PO and PR. So far we had only success with PO creation. When a SC is created without vendor details, i am able to see the backend document details in BBP_PD. But still couldn't figure out the reason why it is not passed to ECC.

Your inputs are much appreciated.

Thanks

Kumar

[former_member183819]

>

> Hi Muthu,
> 
> Thanks for the details,
> 
> We are using Classic Scenario, the business scenario we have adopted is:
> when SC is created without vendor details (described as text requirement), a PR should be created in the Back end system.-
After approving the cart what is the status of shopping cart. Did you do any sourcing configuration, I am interested in the sc item status after approval. Did you click item data in the BBP_PD and can you see the some pr number . Atleast PR number issue or not
> When SC is created with Vendor details (Contract, Purchase Info record), a PO should be created in the Back end system.
> 
> We have defined number ranges and document types for both PO and PR. So far we had only success with PO creation. When a SC is created without vendor details, i am able to see the backend document details in BBP_PD. But still couldn't figure out the reason why it is not passed to ECC.
> 
> Your inputs are much appreciated.
> 
> Thanks
> 
> Kumar

[Former Member]

yes, i could see a PR number with all this additional details as below.

Table BBP_PDBEI

CLIENT 453 Client

GUID 4CAEFA58EB9D005CE1008000AC1C2031 Globally Unique identifier

BE_LOG_SYSTEM QA1400 Logical System of Logistics Backend

BE_OBJ_ITEM Follow-On Object Item in Back-End System

BE_OBJECT_TYPE BUS2105 Follow-On Document Object Type in Back-End System

BE_OBJECT_ID 2000000167 Follow-On Document Object ID in Back-End System

BE_REFOBJ_TYPE Reference Object Type in Back-End System

BE_REFOBJ Reference Object in Back-End System

BE_REFOBJ_ITEM Reference Object Item in Back-End System

BE_REFOBJ_SBITM Reference Object Sub-Position in Backend System

BE_REFOBJ_TYPE2 Reference Object Type in Back-End System

BE_REFOBJ2 Reference Object in Back-End System

BE_REFOBJ_ITEM2 Reference Object Item in Back-End System

BE_REFOBJ_FYEAR2 0000 Reference Document Object - Fiscal Year in Back-End System

BE_STGE_LOC Storage location

BE_PLANT 2016 Plant

BE_BATCH Batch Number

BE_VAL_TYPE Valuation type

BE_MOVE_REAS 0000 Reason for Movement

BE_EXPERYDATE 00000000 Shelf Life Expiration Date

BE_PUR_GROUP 206 Purchasing group

BE_PUR_ORG 2000 Purchasing organization

BE_CO_CODE 2000 Company Code

BE_DOC_TYPE CLRQ Purchase Requisition Document Type

BE_ACCREQUIRED Account Assignment for Logical Backend Required

BE_SP_STK_IND Key for Special Stock Section

BE_INFO_REC Number of purchasing info record

BE_MOVE_TYPE 201 Movement type (inventory management)

BE_PACKNO 0000000000 Package number

BE_INTROW 0000000000 Internal line number for limits

BE_ITEM_TEXT Short Text of a Service Purchase Order Item

BE_PO_PRICE 1 Price from Backend

BE_UNLOAD_PT 200 Unloading Point in Backend

BE_DEL_IND Deletion Indicator in Backend Documents

BE_TRACKING_NO Requirement Tracking Number

BE_COND_TYPE Condition Key

BE_COND_STEP 000 Level Number

BE_COND_COUNTER 00 Condition counter

[former_member183819]

Yes. Your PR number also created 2000000167. but it was not reached your concern.

any error in the RZ20 .

PR number created and it must transmitted to ECC as you expected.

some times numbers generated but still some data could be wrong. can you check any error in rz20 /sm58

hope you would have keep the same number range in ECC and make them EXTERNAL.

http://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination

Muthu

[Senthil_Van]

Hello Muthu,

Here is the RZ20 error details.

Date 08.10.2010

Node name (MTE) BI1\Business to Business Procurement(453)\...\Shopping Basket\Backend application errors

Time 19:01:07

System BI1

Context Business to Business Procurement(453)

Object name Shopping Basket

Short name Backend application errors

Status ACTIVE

Alert text Shopping cart 1000001182 (PReq. 2000000167): BBP_BD 002 An exception has occurred

Value 3

Severity 50

Status Set By SB_Backend

Status Set On 08.10.2010

Status Set At 17:01:07

Msg class SAP-T100

MsgID BBP_ADMIN 015

VAR 1 1000001182

VAR 2 2000000167

VAR 3 BBP_BD 002 An exception has occurred

VAR 4 00000000000000000000000000000000

Client 453

User WF-BATCH

[former_member183819]

this piece of error is Inscrutable

create another material or describe procurement free tet shopping cart.

let us confirm tat we have issue for all PRs .

make ensure that all piece of data is correct in account assignment like cost center /gl account too

Muthu

[Senthil_Van]

Hi Muthu,

I created a SC using Text description with all account assignment details except supplier info, i still couldn't get the PR created in back end.

Then i went into the SRM Config and made the config as below

Spro ->define objects in backend -> to always external procurement and always PR.. no success with this setting as well.

In case of SC to PO i can see the XML in SXMB_MONI but with PR no XML is generated or neither the Idoc. Is there any Badi activation or changes involved in table 'BBP_FUNCTION_MAP', the current settings are shown below.

BUS2012 CreateFromData1 ERP_3.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

BUS2012 CreateFromData1 ERP_4.0 /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP

BUS2012 CreateFromData1 NON_SAP_1 NOR3_PO_CREATE

BUS2012 CreateFromData2 ERP_4.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

BUS2105 CreateFromData1 ERP_3.0 CL_BBP_BS_ADAPTER_RQ_CRT_470

BUS2105 CreateFromData1 ERP_4.0 CL_BBP_BS_ADAPTER_RQ_CRT_470

BUS2105 CreateFromData1 NON_SAP_1 CL_BBP_BS_ADAPTER_RQ_CRT_NOR3

US2105 CreateFromData1 R/3_4.70 CL_BBP_BS_ADAPTER_RQ_CRT_470

We have Workflow configured to Auto approval for all our SC scenarios.

Thx..

Senthil

Edited by: Senthil Kumar on Oct 15, 2010 12:47 AM

[former_member183819]

Yes. you also tried your best and drilled every thing.

i am also wondering why PR not yet created successfully.

since all your settings are correct and SRM also issue number range for that PR .

while deduging what happens.

it is indeed insrutable . create oss message as well.

As per our understanding EHP4 -ERP 4.0 PO using SOA technology but PRs not usingf SOA ...technology

Indeed which BAPI is calling

CALL FUNCTION 'BAPI_PR_CREATE1'

DESTINATION av_rfc_dest

Note 1312947 - Wrong business function assigned for service processing

Note 1446742 - Purchase requisition with new MM BAPI for service documents

You are using the CRM service scenario with logistics integration in the back-end ECC system. There two BAPIs are provided for the purchase requisitions (PReqs) in materials management (MM).

1. BAPI_PR_CREATE

2. BAPI_REQUISITION_CREATE

As of ERP Release SAP_APPL 604, PReq posting for services is released via BAPI_PR_CREATE.

Muthu

[Senthil_Van]

Hi Muthu,

Quick question...Do you happen to know the iDOC message type that I need configure in the SRM outbound of WE20 and the Inbound message type of ERP?

Currernt setup:

SRM Outbound message type:

RSRQST

ERP Inbound Message type:

BBPCO

BBPIV

MBGMCR

SYNCH

Much appericated.

Thanks,

SK.

[former_member183819]

not required.

BBPIV - for invoice posting from SRM to ECC

MBGMCR - good receipt from SRm to ECC

since you have explored well already

PR not at alll created.PO created well

as per peter nowat instruction in the link you can debug

Define Number Ranges per Backend System for Follow-on Docume

check this above node too

logical system nu range po numbe pr

xxxxxxxx100 interval numbers of PO and PR.

every thing is correct in your case since PR number also issues but indeed it was not trigeered in ecc side pr correctly.

CHECK ANY LOG IN SLG1 ,SM58

Muthu

[former_member183819]

>

> Hi Muthu,
> 
> I created a SC using Text description with all account assignment details except supplier info, i still couldn't get the PR created in back end. 
> Then i went into the SRM Config and made the config as below
>  Spro ->define objects in backend -> to always external procurement and always PR.. no success with this setting as well.
> 
> In case of SC to PO  i can see the XML in SXMB_MONI but with PR no XML is generated or neither the Idoc. Is there any Badi activation or changes involved in table 'BBP_FUNCTION_MAP', the current settings are shown below.
> 
> BUS2012	CreateFromData1	ERP_3.0	CL_BBP_BS_ADAPTER_PO_CRT_ERP10
> BUS2012	CreateFromData1	ERP_4.0	/SAPSRM/CL_SOA_ADPT_PO_CRT_ERP
> BUS2012	CreateFromData1	NON_SAP_1	NOR3_PO_CREATE
> BUS2012	CreateFromData2	ERP_4.0	CL_BBP_BS_ADAPTER_PO_CRT_ERP10
> 
> BUS2105	CreateFromData1	ERP_3.0	CL_BBP_BS_ADAPTER_RQ_CRT_470
> BUS2105	CreateFromData1	ERP_4.0	CL_BBP_BS_ADAPTER_RQ_CRT_470
> BUS2105	CreateFromData1	NON_SAP_1	CL_BBP_BS_ADAPTER_RQ_CRT_NOR3
> US2105	CreateFromData1	R/3_4.70	CL_BBP_BS_ADAPTER_RQ_CRT_470
> 
> We have Workflow configured to Auto approval for all our SC scenarios.
> 
> Thx..
> 
> 
> Senthil
> 
> Edited by: Senthil Kumar on Oct 15, 2010 12:47 AM

I am suspecting like you ehp3 and ehp4 the below class is missing for creating Purchase request.

CL_BBP_BS_ADAPTER_RQ_CRT_ERP10 rather than CL_BBP_BS_ADAPTER_RQ_CRT_470

CL_BBP_BS_ADAPTER_RQ_CRT_ERP10CREATE_DOCUMENT

I am wondering why it is missing for you ..

---

see our mentor earlier reply

please look at the table BBP_FUNCTION_MAP, and execute it with the parameters:

Objekttype BUS2105, Method CreateFromData1. You will get the result:

Adapter

CL_BBP_BS_ADAPTER_RQ_CRT_470

CL_BBP_BS_ADAPTER_RQ_CRT_470

CL_BBP_BS_ADAPTER_RQ_CRT_470

CL_BBP_BS_ADAPTER_RQ_CRT_NOR3

CL_BBP_BS_ADAPTER_RQ_CRT_31I

CL_BBP_BS_ADAPTER_RQ_CRT_31I

CL_BBP_BS_ADAPTER_RQ_CRT_40B

CL_BBP_BS_ADAPTER_RQ_CRT_45B

CL_BBP_BS_ADAPTER_RQ_CRT_45B

CL_BBP_BS_ADAPTER_RQ_CRT_46C

CL_BBP_BS_ADAPTER_RQ_CRT_470

With the BAdI BBP_DRIVER_DETERMINE you can overwrite these adapters. So in case you have the backend release ERP_1.0, then the CL_BBP_BS_ADAPTER_RQ_CRT_470 will be assigned by default.

If you call this driver CL_BBP_BS_ADAPTER_RQ_CRT_470 in the SE24, doubleclick into the method CREATE_DOCUMENT. There you will see how the BAPI_REQUISITION_CREATE is called.

But now back to your question, you have two option

- if you use the BAdI BBP_DRIVER_DETERMINE, you need to copy the CL_BBP_BS_ADAPTER_RQ_CRT_470 (or other one, depending on the release of your backend system) e.g. into Z_CL_BBP_BS_ADAPTER_RQ_CRT_470. In the CREATE_DOCUMENT of your method Z_CL_BBP_BS_ADAPTER_RQ_CRT_470 you can change the BAPI_REQUISITION_CREATE to something else.

- you can modificate directly the CL_BBP_BS_ADAPTER_RQ_CRT_470, that it calls your user defined BAPI.

--