SRM - unable to create ECC PO from SRM RFx Response

[Former Member]

Hi all,

I am on SRM 7.02, Level 5 (SAPK-70205INSRMSRV) using the classic scenario, using bidding in SRM server.

process

• SC created in SRM - > SC goes to sourcing -> buyer creates RFx -> RFx is sent to bidder -> bidder processes RFx Response -> buyer accepts RFx response -> buyer creates follow on document (PO) from RFx Response (create PO).

problem:  once the buyer clicks "create purchase order" from the Accepted RFx response, the system throws a green checkmark message "Purchase order cannot be created as there are no items" (message number is /SAPSRM/PDO_QTE 069), even though there is 1 line item.  The ECC PO is therefore NOT generated.  since this is the classic scenario, an ECC PO should be created directly.

my set-up

• I have set up internal number range in SRM (Define Number Ranges for Shopping Carts and Follow-on Documents) PO 4300000000 4399999999
• I have set up the same number range (external) with separate document type "ZSRM" in ECC
• I have assigned "ZSRM" order type to attribute DP_PROC_TY in SRM org structure (ppoma_bbp)

Am i missing anything?  what could be causing this error?

cheers,

[Former Member · Accepted solution]

hi all,

we are able to get a step further, however, still have an issue.

once we click the "create Purchase order" button or "simulate purchase order button" in the  "display RFx response' screen, the system provides this message: "PO XXXXXXXXXX is in the process of transfer to back-end system", however, the PO is NOT replicated. Also, there are no errorlogs / messages in RZ20 / applicatin monitor that indicate how to resolve.  If you look in BBP_PD, at supplier quote, it is stuck in status I1111 (Item in Transfer Process).  Any ideas on how to debug / trouble shoot this, or what could be causing the error?

cheers

[former_member208244 · Accepted solution]

Hello Aleem,

Do you solved the first issue by adding the correct attributes to the RFC user who transfer the PRs from ECC to SRM?

So, to give you a valuable input I need a little more information about your scenario.

Check following points and tell me the results:

- Are you using CPPR scenario in the transfer of PRs to SRM?

- Do you properly configured the backend system by product categories?

- Do you have PI active?

- What system type do you have configured for the backend (ERP)?

For the SRM deployment I understand you have, the transfer of PO will be  using XMLs.

- Do you have configured the xml messages for PO output (PurchaseOrderERPRequest_v1) and all the business scenario linkage in PI?

- Did you checked the transaction SXI_MONITOR to find the current XML regarding to the PO?

Kind Regards,

SG

[Former Member · Accepted solution]

i resolved the first issue by creating a transaction type for PO in SRM.

i am not transfering PRs to SRM...the process is:

process

• SC manually created in SRM - > SC goes to sourcing -> buyer creates RFx -> RFx is sent to bidder -> bidder processes RFx Response -> buyer accepts RFx response -> buyer creates follow on document (PO) from RFx Response (create PO).

yes, i have properly configured product categories - I am currently able to replicate shopping carts in requisition.

system type is ERP_6.0 for my backend ECC system (EHP6 FOR SAP ERP 6.0).

Is PI a requirement for this scenario?  I thought it was not.  Shouldnt the replication follow through RFC, just like replicating a requisition / PO from a shopping cart?

cheers.

[former_member208244 · Accepted solution]

Hello Aleem,

The scenario uses PI.

Check SMQ1/SMQ2 and SXI_MONITOR and if you do not have anything then check ST22, SM21, SLG1 or RZ20 por Purchase Order monitor.

Regards,

SG

[Former Member · Accepted solution]

is there any way to manage this scenario without PI?  We are not transferring any PReqs from ECC to SRM...we are only replicating POs directly from RFx Response (using SRM classic scenario)

[former_member208244 · Accepted solution]

Hello,

Choose backend ERP_1.0  or 2.0 or 3.0, in BBP_FUNCTION_MAP for these backend have the function B46B_DPO_TRNASFER.

Tell me the results,

Kind Regards,

SG.

Message was edited by: Zoltan Keller

[Former Member · Accepted solution]

Hi,

There is a badi that you can implement if you intend to keep the system type to ERP 6.0 ( maybe for some other transfer eg Contracts)

BBP_DETERMINE_DRIVER

and change the driver name and backend system type here for a specific type of object( in your case Purchase order)

Regards,

Naveen

[Former Member · Accepted solution]

hi,

once i changed the system type to ERP_3.0, i get an error, which seems better, as at least it seems the system is attempting to replicate the PO:

this is the error i get:

TD 600 Text * ID * language * not found

any idea of how to fix this?

cheers.

[Former Member · Accepted solution]

i resolved the error...debugging found that the error in RZ20 ("TD 600 Text * ID * language * not found") was a very misleading error...the real issue was that the shopping cart document type was defaulted in attributed BSA...after removing default, PO was able to be replicated...

[former_member201356]

I am also facing the same  issue

Please provide your inputs, I  checked the number range and transaction types in ECC and SRM everything looks fine ..pls guide

[Former Member]

I mentioned above...we debugged it, and found that the SC doc type was defaulted in attribute BSA; after removing default, the PO was able to be replicated.

[former_member201356]

Hello Aleem,

Thanks for your reply.

For my case Iam seeing the PO in XML monitor in ECC, the PO struck with some data errors like "Invalid G/L account", "plant is not responsible for purch org", "invalid Purch group".

While creating the auction we cannot give G/L account -- not sure how to over come this.

Other errors like Invalid Pgroup evenn though the Pgroup exists in ECC.

Any inputs please.

Thank you

Regards

Srinivas G

[former_member774668]

We have the same message "PO XXXXXXXXXX is in the process of transfer to back-end system", however, the PO is NOT replicated to in any of the systems (SRM or ERP). To attribute BSA indicated one value "NB", the "Default" is not check.

There is no other error, please help.

[Former Member]

I think we removed the value of BSA entirely.  After that, it worked for us.  Give that a try.

[Former Member]

hi,

We didn't use XML/PI for this scenario, so my scenario is different from yours. 

What SRM version do you have?  Did you create your auction with reference to a Shopping cart?  Does your shopping cart have a GL account assigned to it (indirect / service item), or is it for a stock  (direct) item?  If you are using a direct item, do you have customizing switch SRM_702_DIRECT_MATERIAL activated?

Please double check your ECC org structure to ensure your POrg is responsible for the plant you are using, and also ensure your SRM org structure is correct (Pgroup to POrg assignment, and locations (plants) are assigned correctly).  If they are correct, then get a developer to debug, because in my experience, the error messages returned by SRM are not always correct and can be misleading.

Cheers,

AD

[former_member774668]

Removed the value of BSA entirely - did't help

My process: buyer creates RFx -> RFx is sent to bidder -> bidder processes RFx Response -> buyer accepts RFx response -> buyer creates follow on document (PO) from RFx Response (create PO).

If we activate the extended classic scenario, the PO is replicated to both systems (SRM or ERP), еhere is no other error.

In classic scenario we have a problem, PO is NOT replicated to in any of the systems.Today checked SC, if SC manually created in SRM - its replicated to both systems (SRM or ERP) in classic scenario.

[former_member774668]

1. We have RFC-connection

2. SRM version - 7.13

3. RFX manually created in SRM, isn't reference to a Shopping cart

4. SRM_702_DIRECT_MATERIAL activated

5. org structure is checked

Regards

[former_member208244]

Hi Viachaslau,

You need to populate attributes in your purchaser user in SRM to default account determination and allow creation of POs in Backend without SC.

Regards

SG

[former_member774668]

Hi Sebastian

You mean the attribute REQUESTER?

Regards

VG

[former_member208244]

Hi,

I mea, the account assignment attributes like default cost centers and etc. As you don't have XMLs and no Direct material you must assign an account assignment, when no SCs in play, then default account details in your PPOMA_BBP position is required.

Regards

SG

[former_member774668]

Default account details in PPOMA_BBP there's. I have not filled the attribute REQUESTER, maybe because of this problem?

Regards

VG

[former_member208244]

Hi,

REQUESTER is just for shop on behalf.

Please check next points:

Customizing:

Proper Product Category to GL configuration done

User attributes:

Default account assignment category

Default cost object assigned

Kind Regards

SG

[former_member774668]

Check

Regards

VG

[former_member201356]

on the same topic, how  the G/L will  be fetched is it from the requestor account assignment or froom the product that  used in the bid ?

currently in my case there was a CC default which I removed but now the PO is automatically taking the account assignmet as "P" ( WBS related) .

doo we have any option like forcefully  process the XML in ECC and create the PO in  held status that really helps for our requirement

[Former Member]

Hi Aleem,

we are facing the same issue reported in your first post (Purchase order cannot be created as there are no items).

Could you kindly give us advise on how you fixed this?

Thanks a lot!

Ci

[Former Member]

changed system type to ERP_3.0.   See note above.