I had this document and gone through it already. This document just tell us how to use the 5 user defined customer fields, that we have used up already.
We have allready used the 5 standard customer fields in the catalog and want a new one.
We use the standard for
- "Asset class",
- "No control" (for workflow),
- "Approval" (for workflow),
- "GL account" (different GL account within same UNSPSC class)
- "High Level Articles" which control workflow and it is possible to change price and vendor in SC.
Then I need a new field for a responsible purchasing department (purchasing group). When a user buy an article with an responsible purchasing department the SC must be approved first before it runs the normal workflow.
For the above new fields I therefore need 6 customer fields.
The question is, can I create a new customer field or do I have to use a standard field in catalog and transfer this to a new field in SC??
The user has an purchasing group assigned and this will be populated into the SC. What I need is another purchasing group which are responsible for the article and must approve the buying before the workflow runs into the normal workflow (lookup in the org. structure).
Maybe if I have the possiblility to assign an UNSPSC code to an purchasing group or org. element it can solve my problem but I dont know anywhere to maintain this link.
The structure BBP_WS_OCI_ITEM_S has a CI include namely CI_OCI_CUSTOMER_EXTENSION. You can try to add fields to this and give it a try. You need to make appropiate changes in CCM as well I suppose.
My question is what is the use of that purchase group data in inbound OCI . However we are going to determine the purchase group depends upon product category settings in org . structure while creating sc. i do agree if he brings some critical data which is not used but badly required his business.
Thank you all for your answers and good proposals.
I have solved this in another way by creating a table in SRM instead of extend the OCI.
As I wrote I need a responsible purchasing group to approve the buying before it went into the normal workflow for approval. The tabel contains a specific UNSPSC code or a range of UNSPSC codes where a responsible purchasing group is assigned. My workflow now reads into this table before the normal workflow runs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.