on 04-26-2016 2:55 PM
Hi,
In our C4C project we are not using a middleware (neither HCI nor PO) for integration to SAP ERP (I know, I know; not best practice, but as a consultant I'll have to move on). Customer has lots of z-fields in their landscape and possible input values of those fields are a lot (for ex, a z-field has more than 100 possible values). In our project scope, all of this functionality will be handled in C4C, so we are creating new fields via Studio.
Now our question is, how would it be possible to maintain the possible codelist values for those fields in runtime, dynamically? What should the data type for this Z-field be, and how can we read the possible values of that field from its customizing table in ERP on runtime and validate the field on C4C accordingly?
Fyi: For starters, we created a remote Z-function in ERP with an importing parameter as table, and when you give the customizing table name to this function, it returns the possible values of that table. We can create a web service for this function, but how do we call it from the codelist functionality?
Hello Kivanc,
Sorry,but the PDI is not supporting the filling of codelist values dynamically.
You do not have a dynamic codelist provider in PDI.
Sorry,
Horst
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Horst,
Thank you for your input.
Seems like so, yeah, so we thought about implementing this in another way: Creating new business objects representing Z-tables, and filling their possible values of those by a z-program (background job). But as you may tell, we couldn't create association from xbo to a business object. Does anny workaround to handle this come to your mind?
Hi,
Our BO is customer (BusinessPartnerGlobal), so I guess this does not help us; while trying to create association we get a standard error "you cannot create an association to a business object from extended business object" (I'm not exactly sure about the error message's content, but it's basically saying this).
Hi
I guess now I understand your question
If you have an extended field of type code and you have enhanced the standard UI say quick create
On QC this field will a dropdown, when I click on this dropdown it should same value maintained in ERP. I
Then you should create a custom BOs for each code list, each custom bo will contain data for each code list.
And Create a OVS on each custom BO
and in xbo just use field of type ID or Description and make this field as OVS type and assign OVS to field.
To maintain data in custom bo you should create MDR which keep updating each BO by using web services provided by ERP system.
Regards
Sunil
Hi Sunil,
Can you please elaborate on this sentence a little bit: "in xbo just use field of type ID or Description and make this field as OVS type and assign OVS to field." -> Our developer couldn't understand exactly what you've meant here.
How to make this field as OVC type and assign OVS to field?
Thanks,
Hi,
You can create Business Configuration Object (BCO) and use it as a datatype in your xbo. The bco data can be maintained in Business Configuration Fine-Tuning. It is not possible to maintain the values dynamically via scripting/coding, you will have to maintain manually via cloud studio / fine-tuning.
As for UI, if you want to display the field as dropdown list, you will have to create EC for it. Enhancing standard UI screen with custom PDI field does not support dropdown value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.