Extended classic scenario - no backend PO created

[Former Member]

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.

I get following error messages in application monitor as backend application errors:

No instance of object type PurchaseOrder has been created. External reference:

PO header data still faulty

Document number 100000093 not within defined inter val

What's going wrong here?

Hubert

[ricardo_cavedini · Accepted solution]

Hello,

Check if you have set up the customizing as below:

Extended classic scenario:

a) at SRM side:

- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.

- Create a number range for a local PO.

- Assign the local PO number range as a internal numer range to the transaction type.

b) at R/3 side:

- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)

- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)

- Make sure that the SRM and R/3 number ranges match are exactly the same.

Kind regards,

Ricardo

[Former Member]

For information .

In classic scenario:

a) at SRM side:

SPRO activity "Define Transaction Types":

- The name of SRM transaction type corresponds to the same name of the

document type on R/3 side.

- To assign the transaction type to the classic scenario you have to

maintain the transaction type name (= the R/3 PO document type) to the

attribute BSA in PPOMA_BBP.

- You must enter the following as interval numbers:

Exactly the value Int.No. of the shopping cart transaction type that was

defined in activity Define Transaction Types.

LO for local purchase orders

RQ for purchase requisitions in the backend system

PO for purchase orders in the backend system

RS for reservations in the backend system

- These number ranges you can see in SPRO activity "Define Number Ranges

for Shopping Carts and Follow-on Documents":

b) at R/3 side:

- Enter the Number Range (corresponding to the SRM number range PO) and

flag it as an external number range (trx. OMH6 Number Range for

Purchasing Documents)

- Maintain the document type corresponding to the SRM transaction type

and assign the R/3 number range for POs as "NoRge Ext" (field

V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)

-Make sure that the SRM and R/3 number ranges match are exactly the

same .

Regards

Lauren

[Former Member]

Hi,

all settings checked and everything seems to be ok. But I get still following message:

Error reading the export data for EXEC transfer of purchase order 7000003392

Hubert

[Former Member]

Hi Hubert,

Can you check BBP_PD for this PO. Check if any furhter error captured there, also check if any more GUID is created.

If you find any furhter GUID, then click on the same and check if any error you can see along with the recent GUID.

Secondly, you need to check vendor status in both the systems i.e. SRM and backend. Vendor should not be archived/bocked in any system. Check with the status of cost elements like if you are using WBS/Orders etc. Check the status of the same in the backend system. These elements should not be locked.

Let me know your findings.

Cheers!

Sachin

[Former Member]

Hi,

I just used BBP_PD and tried to check document, got following message:

Error in backend communication; inform system administration

Message no. BBP_CF005

POs in classic scenario are created, account assignments are ok and not blocked in backend!

Hubert

[Former Member]

Hi,

Error in communication is due to RCF connectivity to backend system. Check the RCF connection test mode in SM59 in your SRM system. If the connectivity is now okay, then you need to execute function module BBP_PD_PO_TRANSFER_EXEC to push the PO from SRM to backend system.

Cheers!

Sachin

[Former Member]

Hi,

In my previous reply, read RCF as RFC...its typo.

Sachin

[former_member183819]

check number range between both srm and ecc systems.

since srm is maste rsystem to create numbers for PO bo.

[former_member324993]

Did you check the po ?