cancel
Showing results for 
Search instead for 
Did you mean: 

MDGC missing field during SMT mapping

former_member283411
Participant
0 Kudos

Hello Experts,

we are implmenting MDGC 7 as a demo system and would like to add a developed field of KNVV table to the change request UI. However, we are facing two major problems:

1. when we extend the BP data model, entity type BP_SALES, the structure/Table field should be filled by us or it should be generated automatically? (marked with red on the picture what i mean)

2.  we are trying to do SMT mapping in CUST_BP_SALES_2API but in mapping steps CMDS_EI_SALES_DATE we got stucked. Our custom field does not represent in the list during field selection:

Could you please help on what could be the reason of the error in these cases?

Many thanks in advance,

Tamas

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Steps to follow for adding a Custom Field:

1. Add a Custom Field to Data Model

2. Activate the Data Model

3. Generate the Structures (Structure Generation add custom to standard MDG Structures - usually type     PP, ES, FP & KY are re-generated)

4. SMT Mapping : After the previous step is complete, now the fields will be available for mapping.

former_member283411
Participant
0 Kudos

Hi Archana,

many thanks for the answer. The solution we found is that

  1. we have incorrectly appended and hence couldn't properly activate the append in KNVV table, beacuse for database fields, custom namespace is not Z* or Y*, but ZZ* or YY*. That's why even the initial append was not correct.
  2. manually appended the mapping structures which didn't contain our field (we wanted, but couldn't select our fields from the drop-down during the mapping steps descrbed here:http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0375d58-2161-2f10-e285-c6078fcb8.... I don't know if it was good or bad, but it works now.

All in all, what we did was the following:

  1. Apended KNVV with 2 new fields: mind the naming convection !! (ZVAT not correct ZZVAT is correct)
  2. Added the new fields to the BP_SALES entity type of BP data model (as attributes)
  3. Activated the data model
  4. Generated data model sprecific structures (here we only selected BP_SALES)
  5. Did the SMT mapping correction steps listed in the above document (both API and STA), but for that we have appended the relevant structures whereever we had a missing field
  6. Then 'ADjust staging area of linked Change Requests" in 'Edit data model' IMG option
  7. Then we opened the sales area data UI screen in customizing mode and added the new elements (fields). It works fine.


Thanks,

Tamas