on 03-23-2011 11:00 AM
Hi,
Iam doing external sourcing scenario, After creating the PR I am it is showing succesfully updated in SRM and data is available in BBP_PD but I am unable to see the Shopping cart created in Portal carry out sourcing.
I checked in Table BBP_PDIGP X indicator is not updated in field SOURCE_REL_IND.
Some one please suggest what mistake I am doing.
Regards
MMR
Hi
Define sourcing for product categories setting is important.
since your carts are available in SRM without any issue. but it is not available in the cockpit.
Are all the carts are not setting sourcing indicator ? or only some carts are not venturing to the cockpit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The status is showing as below
HEADER I1021 Created
HEADER I1038 Complete
HEADER I1106 Shopping cart ordered
HEADER I1129 Approved
The scenario is like this presently our client is using one company code where entry channel & EBP-Extrenal channel mapping is done properly and it is working fine, now we got a requirement for rollout the same functionality for new company code.
For this we configured new company code org structure with purchase org and pur group etc.
after doing this we are getting this problem for the new org. structure, old one it is working fine.
Regards
MMR
Hi
I am "Manjunath" not Muthu :-).
In PPOSA_BBP check if you have assgined the RFC user, if not then do the following:
Using transaction users_gen in SRM assign the RFC user to one of the Ogr. unit which in turn creates the psition and assigns the RFC user to this newley created postion assign the Co.Code that is newley created in the attribute of the Co.Code.
with regards
Manjunath
Hi Manjunath,
Sorry in hurry I not checked the reply given person, thanks for your reply.
Please find the org. structure I defined and please sugget me what mistake I am doing.
Level1 (Root organisation) -
Company(Not maintained any attributes)
Level2 -
C.code1(Maintained attributes c.code1),
C.code2 ()Maintained attributes c.code2),
EBP_EXT_Channel (Maintained both c.codes),
Entry channel (Maintained both c.codes) this is created with Users_gen.
Level 3 -
P.org1 (C.code1),
P.org2 (C.code2)
Level4 -
P.grp1 (P.org1),
P.grp2 (P.org2)
Level5 -
Buyer user
Approver user
Please suggest is there any thing I missed out.
Regards
MMR
Dear Manjunath,
The configuration for the back endsystem is maintained as below.
P.Group Category Id Source system Int. proc Ext.Proc
* ECC System 3 2
Please suggest is any corrections required.
Is it ok I maintain a single entry channel for both company codes.
If I create a new entry channel for new org. structure is with new RFc user is there any problem please suggest.
Regards
MMR
Hi
With your config settings there is also a chance of PO getting created from SC after approval without going to Souricng, please check if the PR or SC has a fixed vendor. In BBP_PD check for the respective SC a PO is created or check the follow on documents.
One RFC user will suffice both co.codes.
with regards
Manjunath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.