Assignment requirement

[Former Member]

Hi All,

Can we have an assignment to check what was the last assigned number.

Eg:

I have an account group 0001, for which i maintain a range say (from number - 100 to number - 500)

to begin with i have assigned 100 to a vendor using assignment, so when i create a new record can i check what my last assigned number was?

Rgds,

Sharma.

[Former Member · Accepted solution]

Hello,

Why do yo wanna, check the last number assigned, please explain your scenario.

As explained by Neethu, in point 2

if you have PI in the system landscape and are using workflows, just trigger a XML back to MDIS, with vendor number , you need not have change pointer activated.

Regards,

Abhishek

[Former Member · Accepted solution]

Hello Abhishek,

I wanted to check the last number assigned so that i could run an assignment to increment the number by one for my next record.(so that i would be able to assign numbers automatically just by running an assignment)

however i understand that the assignments are run recordwise and not field wise so i can achieve this by the two methods specified by Neethu joy. or by API's

Thanks and regards,

Sharma

[Former Member · Accepted solution]

Hi Sharma,

I hope you are using MDM as central hub to create and Update master records and then syndicating it back to source system.

You must be having some governance set up for this process.

Now I suggested you two options one to use qualified Number Range and another one using PI.

Lets assume for acoount group 001 u have number ranges in source system as 100 to 500.

Option 1 using Qualified Number Range:

You need to configure number range 100 to 500 for particular remote system and account group 001.

Now a master record is created in MDM and once it pass through governance setup and is syndicated to Remote system.

Vendor Number 100 will be assigned but as source system uses internal number range this vendor number will not be accepted .

When we use this option we need to make source system and MDM Number range is sync i.e. if already 100 vendors are existing in source system then 100 to 200 number is already consumed.so when u start creating vendor is MDM u need to configure number range from 200 to 500 so this way we maintain sync between MDM and source system.

But if your number range is alpa numeric this method cannot be used.

Option 2

Vendor record is created in MDM and vendor number is left blank and syndicated to Source system.In source system Vendor number is generated.Now you need to update the ssame in MDM.

You can either do it through PI using change pointer which will trigger xml file with vendor number and MDMID (or any unique field )in MDIS(which u need to configure for automatic import) .

or

You need to create some user exit in source system so when new vendor is created in source system it should trigger or call API to update the vendor Number in MDM.This process will nto require PI.

Depending upon your landscape you need to opt for right option.

Regards,

Neethu Joy

[Former Member · Accepted solution]

Hello,

For auto increment, MDM has Auto ID, you can find details of the in the MDM Console Guide or a simple google will provide ample documents.

What this field is in simple words is an Auto Increment Field for ever records, you dont need a assignment for this.

Also as suggested as Neethu, these options are required when you wanna synchronize the Vendor Number or Custom Number with the SAP R/3 System, since we need to maintain Internal Number range in SAP R/3. So we require Qualified Number range to be maintained to match that in MDM.

You use MDM Auto-ID this will auto increment for every new records in sequence.

Regards,

Abhishek

[Former Member · Accepted solution]

Thanks abhishek,

I wanted to define different number ranges for different account groups or material types so i would go with qualified number range option which will generate the numbers upon syndication as per the assigned range .

Regards,

Sharma.

[Former Member]

Hi Sharma,

Assignment executes expression record wise not field wise.It will not be possible to find the last number assigned.

I assume you want to assign vendor number as your source system uses internal number range.

you can achieve this number assignment in 2 ways:

1st Option

Use Qualified Number range and set the number range in console for the account group for the remote system.

But this will assign number only when record is syndicated from MDM.

2nd Option:

when record is created leave the vendor number field blank and syndicate it to source system ,then through change pointer send the vendor number and MDMID(or some unique field) and import it .

I have experience and has worked on both the ways.

Regards,

Neethu Joy