Follow-on documents not created

[Former Member]

Hi experts

In classic scenario after shopping cart aproval the system must create in backend one purchase order.

Please someone check if configurations are correct.

Nunber range for shopping cart:

20 2000000000 2999999999 internal

Transaction Types for shopping cart:

SHC

Int. Number Range 20

Ext. Number Range

Number Range for Local Purchase Orders

40 4000000000 4099999999 internal

Transaction Types Purchase Orders

ECPO

Int. Number Range 40

Ext. Number Range

But when shopping cart is created and aproved no Follow-on documents created

In transaction BBP_PD

Stats:

Status Description Inact

HEADER I1015 Awaiting Approval X

HEADER I1021 Created

HEADER I1038 Complete

HEADER I1106 Shopping cart ordered

HEADER I1129 Approved

In Table BBP_PDBEI

CLIENT ... 500

GUID ... 6F7F5A78C9F6C442AFF

BE_LOG_SYSTEM ... DEVCLNT500

BE_OBJ_ITEM...

BE_OBJECT_TYPE...

BE_OBJECT_ID...

BE_REFOBJ_TYPE..

BE_REFOBJ..

BE_REFOBJ_ITEM..

BE_REFOBJ_SBITM..

BE_REFOBJ_TYPE2

BE_REFOBJ2

BE_REFOBJ_ITEM2

BE_REFOBJ_FYEAR2 ... 0000

BE_STGE_LOC ... 0400

BE_PLANT ... EF04

BE_BATCH

BE_VAL_TYPE

BE_MOVE_REAS ... 0000

BE_EXPERYDATE ... 00000000

BE_PUR_GROUP ... G18

BE_PUR_ORG ... OC01

BE_CO_CODE ... 1000

BE_DOC_TYPE ... ECPO

BE_ACCREQUIRED

BE_SP_STK_IND

BE_INFO_REC

BE_MOVE_TYPE .. *

BE_PACKNO .. 0000000000

BE_INTROW .. 0000000000

BE_ITEM_TEXT

BE_PO_PRICE .. 1

BE_UNLOAD_PT

BE_DEL_IND

BE_TRACKING_NO

Note that are empty.

BE_OBJ_ITEM...

BE_OBJECT_TYPE...

BE_OBJECT_ID...

BE_REFOBJ_TYPE..

BE_REFOBJ..

BE_REFOBJ_ITEM..

Someone have some idea what could be done?

thanks

Nilson

[Former Member · Accepted solution]

Hi

<b>Incase you are using - Standalone Scenario in SRM then you should have:-></b>

BE_OBJECT_TYPE = BUS2201 (local PO)

BE_OBJECT_ID = local PO ID (got it from custo)

BE_OBJ_ITEM = PO item number (should be updated by CLEAN_REQREQ_UP)

Please check it on an exisiting SC transfered correctly into a PO.

In BBP_PD, can you find some header & item links between BUS2121 and BUS2201 ?

Else, you can resubmit the SC transfer with FM BBP_PD_SC_RESUBMIT.

<b>Related links -></b>

<b>In Extended Classic Scenario (ECS) -></b>

1-What message do you have in ST22 or RZ20 ?

If you go to bbp_pd transaction and select your shopping cart, at the bottom of the screen, you should be able to view error message displayed.

2- Did you maintain number range and transaction type configuration ?

3- did you maintain transaction type (example ECPO) in the BSA attribute ?

Please detail your configuration steps in your next reply.

Do let me know.

Regards

- Atul

[Former Member · Accepted solution]

Hi Atul

I am using classic scenario, when I go to transaction BBP_PD there is no links between BUS2121 and BUS2201

Thanks

Nilson

[Former Member · Accepted solution]

Hi

<b>Please check the following SPRO Settings in SRM System -></b>

1) Define number range for Shopping Cart and FollowOn Document by maintaining an additional number range which is used to create PO in backend. Often the number range object is "PO" with a certain number.

2) Check if within the setting in "Define Objects in Backend System" is selected to create a PO.

3) Define Transaction Types by creating Transaction Type ECDP, which then later corresponds to the Transaction Type in the Backend.

4) Go to Backend and maintain the transaction type (ECDP) and the corresponding

number range for Purchase Orders using the number range object used in SRM (e.g. "PO").

<b>In Classic scenario, the PO gets created in R/3 system. For Local SRM POs, you can use BBP_PD Transaction.</b>

Hope this will definitely help. Do let me know.

Regards

- Atul

[Former Member]

Hi

<b>Please go through this -></b>

<u>Purchase requistion Instead of purch order created in backend</u>

A shopping basket item can be created using the catalog or a free form entry and in both cases with or without R/3 material number. In order to create a purchase order you need at least the following data in the shopping basket item:

a) using catalog with material number:
The catalog must pass the R/3 material number, the quantity, the unit of measure (see note 335485). If the vendor and the purchasing organisation are not defined in the customizing "BBP -> Define Catalog",then the vendor also has to be transferred from the catalog.
For the purchase organisation, the system will use the purchasing organisation to which this vendor has been defined. If the vendor has been defined for more than one purchase organisation, then the system will just take one of the existing purchase organisations. Hence, to be sure the system is using the correct one, you should define the purchase organisation in customizing for the catalog.

In the backend a valuation price must be defined in the accounting view in the material master and the material type of the material must allow the value updating (transaction OMS2 in the backend).

b) using catalog without material number:
In this case the catalog must provide the description, the quantity, the unit of measure (see note 335485) and the product category. If the vendor and the purchasing organisation are not defined in the customizing "BBP -> Define Catalog", then please check the information given above in scenario a) for the vendor and purchase organisation.
If there is no source of supply defined in the backend for this material - vendor combination, then you must transfer a price from the catalog. The catalog can deliver some contract information too, but this is not necessary.
c) using product entry with material number:
The material number is obviously necessary, as is the quantity and a valid source of supply (info record or contract). The rest of the data like unit of measure, product category, and description will be taken from the material master.
d) using free form entry without material number:
Here you need the description, the quantity, the unit of measure, the product category and a valid source of supply (info record or contract).

For all items you need of course the accounting data, which can be determined automatically by the system.

Furthermore you have to maintain the following customizing activities:


1. in the EBP Procurement system:
Customizing "-> Define Backend System for Product Category". Please use the F4-help to select the product category.
Customizing "-> Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)" Please use the F4-help to select the purchasing group and the product category.
!!! The documentation of this customizing issue says that you can use the "*" if you do not want to specify a purchasing group or a product category. But this only works well if you set the "*" for EITHER the purchasing group OR the product category. If you use the "*" for the purchasing group AND the product category, then a purchase requisition will be created!!!
Customizing "BBP -> Number Ranges -> Define Number Range for Local Requirement Coverage Request". Here you have to define the number ranges for the documents in the backend. Please read the documentation of this issue carefully.

2. in the backend:
In the BBP Procurement system you define the document type which is used for the purchasing documents in the backend, usually EC. Thus you also have to define these document types in the backend. The creation of a purchase order or a contract release order in the backend is more or less the simulation of the conversion of a purchase requisition into a purchase order/ contract release order. Therfore you have to maintain the item Link purchase requisition - document type in the customizing activities:
"MM -> Purchasing -> Purchase Order -> Define Document Type" (OMEC)
and
"MM -> Purchasing -> Contract -> Define Document Type" (OMEC)
Here you have to allow the conversion of this BBP document type for purchase requisitions, e.g. EC,  into the document types for purchase orders, e.g. EC, and contract release orders, e.g. WK/MK.

The purchase order is created in the backend via RFC. All RFCs are executed in the backend with a specific user that is defined in the transaction SM59 in the EBP system. As this RFC-user creates the purchase order in the backend, he must obviously have the authorisation to create a purchase order. There is a special authorisation for purchasing documents which is maintained as a parameter in the user master. The parameter is EFB. The values for this parameter EFB are maintained in the customizing: Materials Management -> Purchasing -> Authorization Management -> Define Function Authorizations for Buyers
So please check in the backend in transaction SU01 if the RFC-user has the paramter EFB. If not, this is fine. But if he has the parameter EFB, then you must check in the customizing, if this parameter does allow to create purchase orders.

Caution! After the implementation of support package 8 or note 357201 the logic for the vendors has been changed. Thus you have to run some reports as mentioned in note 357201. If not the vendor may not be found in the EBP system. So please check if you have processed all the steps mentioned in note 357201 or in note 371716.

If you have followed all the provisions, above, then a purchase order should be created.

Hope this will help. Do let me know.

Regards

- Atul

[Former Member]

Hi Nilson,

some settings are missing when you want to use the classic scenario. Settings to

communicate to the corresponding backend system are missing. In classic

scenario the PO is created in the backend system. You do not need a local PO in

SRM. Have a logical look into your system to connect the transaction types with

number ranges to the corresponding backend system.

Please check the following:

- Define number range for Shopping Cart and FollowOn Document by maintaining

an additional number range which is used to create PO in backend. Often the

number range object is "PO" with a certain number.

- Define Transaction Types by creating Transaction Type ECDP, which then

later corresponds to the Transaction Type in the Backend.

- Check if within the setting in "Define Objects in Backend System" is selelected

to create a PO.

- Go to Backend and maintain the transaction type (ECDP) and the corresponding

number range for Purchase Orders using the number range object used in SRM

(e.g. "PO").

Cheers,

Claudia

[Former Member]

Hi Nilson,

any update on the issue?

Cheers,

Claudia

[Former Member]

Hi,

Please do the settings in SRM--> Cross Application Settings --> Define Objects in Backend System ( In the External Procurement select always purchase order or purchase requesition along with product categories and purchase group with source system).

I hope it will work.

Award points for the help.

BR,

Vijay Mittal

[Former Member]

Hi Vijay Mittal

Thanks for help me but it's not working, please could you confirm if my number range configurtion is correct, in classic scenario the local PO interval is internal assgned to BUS2201 on interna field ?

Thanks

Nilson

[Former Member]

HI

The error mesage is only this:

Shopping cart 2000000695: Error creating the follow-on document

And in BBP_PD THE FINAL SATUS IS:

I1129 APROVED

Thanks

Nilson

[Former Member]

Hi

<u>Try these OSS Notes -></u>

Note 922383 - Error when creating a blanket purchase order

Note 685790 - SRM30: back. PurGrp not correct if changed in SC

Note 710827 - EBP 4.0 When creating a new PO, status is 'Error in Process'

Note 444761 - Incorrect account assignment when creating backend documents

Regards

- Atul