follow on doc not created

Hello ,

Right now, we’re having some troubles with a Shopping Cart that dosent create any follow on DOc.

Per what I see in BBP_PD:

Stats:

Status Description Inactiv

HEADER I1015 Awaiting Approval

HEADER I1021 Created

HEADER I1038 Complete

HEADER I1106 Shopping cart ordered

SAP Managed Tags:
SAP Supplier Relationship Management

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Your shopping cart is in approval - approve it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

i approved SC

Hi elham,

How about the SC status after you approved it?
Could you please show us the status at both header and item level?

Regards,
Wendy

Hi Wendy

Hello Elham,

Looking at the screenshot it indicates that the SC is not yet approved. As Wendy suggested can you check whether the work item for this SC is currently in approved status.

Regards

Pramod

this is another SC

my Question is why follow on doc doesnt create whats the problem?

Hi,

You expect a PO to be created directly and automatically from this SC, correct?

It seems your SC item is not sourcing relevant.

But please check once the value of field "source_rel_ind" of the SC item.

Also please check in RZ20, ST22 and SM13, whether you are getting any backend error, dump or update error.

Regards,
Wendy

Hi Wendy

u said: But please check once the value of field "source_rel_ind" of the SC item.

i dont know how can i check source_rel_ind"

i assgn vendor to my Sc

-----

i expect po or pr create automatically

i ecpect when i create SC , then PO or PR create in backend

---

we use one clinet and classic scenario

--------

i st22 and sm13 i havent any error

but in RZ20 i have a these erorr

Hello Elham,

Can you check whether the customizations related to objects getting created in the backend is done properly.

SPRO -> SRM -> Cross Application Basic Settings -> Define Objects in Backend System

Also can you check whether the attribute (BSA) is defined properly. This attribute should basically define the document type in R/3 system.

Since you are using the the classic scenario ideally the PR should be created in the backend after the SC is approved. Laso check whether the number ranges in both the systems are in sync.

Regards

Pramod

I am not clear on how to maintain the transaction types in SRM and document type in ECC

any update?

???

Hello Elham,

With respect to the customization there would be entries to be maintained for the following combination (i.e., Responsible Purchasing Group, Category ID and Source System Name).

Now i think you are performing external procurement you need to specify whether

1. The system has to create a PR always in the backend

2. The system is to create PO if the item data is complete and PR incase the item data is complete

Can you please check whether this customization is done and what is the value mentioned in your system.

Further for the attribute BSA can you please check and let know what exactly i maintained in your system prior which we can check whether these customizations are fine and check exactly why the documents are not getting created in the backend.

Regards

Pramod