cancel
Showing results for 
Search instead for 
Did you mean: 

Error in follow on docment.

Former Member
0 Kudos

Hello all,

I m trying to create PO as a follow on document, with vendor added in bid invitation along with po as a follow on document. Could you please explain why system throws an error saying error in follow on documents creation? System details are srm 4.0 (classic) with ECC6.0.

Even if i select po&contract as a follow on documents, in condition type ECPO is not seen.

PS:- Process works well when i go for contract as follow on document.

regards,

Vivek

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Vivek,

is the vendor already available in ECC?

When you create a contract, are you able to fully distribute / create the contract in ECC?

Check the doc type settings for the follow on document in SRM as well R/3. The doc type needs to be maintained in SRM and in ECC with internal number range in SRM and external one in ECC.

Also check the setting for follow on doc type - maintain the respective doc type - e.g., ECPO - as a follow on document for BID.

Cheers,

Claudia

Former Member
0 Kudos

Thanx for your reply, following is the clarification to your doubts

is the vendor already available in ECC? -


yes the vendor is already in ecc, i could successfully create PO, contract in ECC only for this vendor.

When you create a contract, are you able to fully distribute / create the contract in ECC?----


yes the contract is getting created in ECC from ebp

Check the doc type settings for the follow on document in SRM as well R/3. The doc type needs to be maintained in SRM and in ECC with internal number range in SRM and external one in ECC.----


the document types are maintained in ecc with proper external & internal number ranges synchronised in both the systems.

Also check the setting for follow on doc type - maintain the respective doc type - e.g., ECPO as a follow on document for BID----


ECPO & ECDP are maintained as transaction type for purchase order (BUS2201) but not for bid (BUS2202) it is maintained as QUOT.

If possible please explain the procedure to create PO in backend from shoppin cart, Direct PO creation for a vendor and through sourcing. (Classic scenario)

Regards,

Vivek

Former Member
0 Kudos

Also check the setting for follow on doc type - maintain the respective doc type - e.g., ECPO as a follow on document for BID----


ECPO & ECDP are maintained as transaction type for purchase order (BUS2201) but not for bid (BUS2202) it is maintained as QUOT.

Okydoky, the missing link is in the definition of the follow on document for BID.

Go to SPRO- Supplier Relationship Management/SRM Server/Cross-Application Settings/Define Transaction Types

The Transaction Object Type BUS2200 u2013 Bid Invitation allows the definition of different variants and the their respective Follow On Documents. In order to be able to create a PO out of a BID (I assume this doc type you are using - counts for every other doc type you want to create a PO from), you need to maintain the linkage to the PO doc type. For BID you need to have an entry in the table for follow on doc with the doc type you want to create the PO, e.g. ECPO.

With this setting you get the entry in the document to be able to create the follow on document and with the selection you then can create the PO.

Cheers,

Claudia

Former Member
0 Kudos

think the follow-on doc customization was missing for BI which you completed after hint from Claudia.

Just to mention you can specify diff doc type of ECC PO with the help of attribute DP_PROC_TY in purchaser grp position.

For procedure to create PO in backend from shoppin cart:

While SC creation in classic scenario SRM can pick up backend SOS (source of supply) like Pur INFO or contract

and if the user completes all necessary data

the SC can be complete.

After the approver approves this SC

with the cleaner job running a BAPI can create PO in backend.

If you have defined the backend object correctly for the prod cat.

For direct PO creation via sourcing

the purchaser will take the requirement (internal or external ) to his/her worklist.

Assign vendor from vendor list or directly.

and if this vendor also exists in ECC for the PORG of the purchaser then PO can be directly created in ECC backend.

BR

Dinesh