Regarding mapping

[Former Member]

Hi All,

I have a infoobject Ex_mat which has Ax_mat as an attribute when I right click on the Ex_mat and choose maintain master data and enter the mat# from my transaction data in the field for Ex_mat it does not match but it matches with Ax_mat so when I design my infosource should I map it to Ex_mat or to Ax_mat.

Thank You.

[former_member188975 · Accepted solution]

Hi Shetty,

You would need to consider the following:

1. The value for Mat # that you entered might not exist in the Ex_mat tables, but still be a valid value...Unless you are sure about the fact that there are different naming conventions for Ex_mat and Ax_mat, like e.g. E_M001 and A_11M.

2. Before you go ahead and map Ex or Ax, you need to be sure of the business meaning of these 2 and the business meaning of the Mat # that you get in the transaction data.

Hope this helps...

[Former Member · Accepted solution]

Ex_mat is the our version of mat# and ax_mat is the cust version of mat#, and i get only the cust version in my transaction data, and how does it look up if the ex_mat tables does not have the value i enter? and i should be able to report on both ax_mat and ex_mat.

[Former Member · Accepted solution]

In this case , I think in the transaction data you need to map it to ax_mat .

But to populate ex_mat also in transaction data you will have to update the master data and have a master data look up in the transfer rules for ex_mat.

Ashish.

[former_member188975 · Accepted solution]

Hi Shetty,

If you are getting values of Ax in the transaction data you should map that to Ax_mat. Then if you also need to have Ex_mat, you can write a start routine to fill up Ex values based on Ax, but there will be an issue if one value of Ax refers to 2 different Ex values...what does your data look like?

[Former Member · Accepted solution]

The master data is already maintained for Ex and Ax, does this make any difference.

[Former Member · Accepted solution]

Hi,

It willl make a difference if you have one value of ax_mat corresponding to 2 values of ex_mat.

You should be fine if you can confirm that every value of ax_mat has a unique value of ex_mat corresponding to it..

Ashish.

[former_member188975 · Accepted solution]

That's good, but to take a simple example, country DE can have currency EUR and country FR can also have currency EUR. So if you hve EUR and look up which country, you have two values and if you need FR, the system will not return this. Similar for your Ex and Ax.

Hope this helps...

[Former Member · Accepted solution]

ex and ax has one to one mapping

[Former Member · Accepted solution]

Ok..

so mapping in transfer rules should be done to ax_mat and do a master data look up to populate ex_mat in the transfer rules.

Ashish

[former_member188975 · Accepted solution]

Then you need to do the following:

Before you load the transaction data, make sure you do the master data load and run the attr change run. Then proceed for the transaction data load. In your Update rule start routine you can write the code to look up Ex_mat value based on the Ax_mat.

Hope this helps...

[Former Member · Accepted solution]

Hey Bhanu,

we surely should join forces..

Ashish

[Former Member]

Hi Shetty,

It totally depends on what is the functionalit of Ex_mat and Ax_mat and what transaction data you are extracting. By seeing the names it looks like custom objects, so check the functionality to decide mapping.

Regards,

Sree

[Former Member]

Hi!

You can not tell without knowing what is the business meaning of these objects. Why does Ex_mat have this attribute, what does it represent? Which object will your users want to report on? Has Ax_mat got an Ex_mat attribute? Do these two objects have other attributes that your users might be interested in?

Kind Regards

Andreas

[Former Member]

Hi,

Could you please clarify ..what Infosource do you mean??

Its a bit confusing..

Ashish..

[Former Member]

sorry its the transfer structure