IDN is not getting auto-activated

[Former Member]

Hello ,

After getting the ASN from a vendor in ECC , the Inbound delivery is created while the same passes to EWM as an Inbound delivery notification.

This IDN gets auto-activated everytime but for the last two days , the user has to activate it manually. Please help for the same.

Thanks

Regards,

rajbharati Sinha

[alex_m · Accepted solution]

Hi,

Go to your IDN using /SCWM/IDN and check PPF tab, whether the PPF action was triggered to activate the IDN and status and application log of the PPF action. You should be able to get the reason.

[Former Member · Accepted solution]

Hi,

Below is the error which i am getting here:

[former_member804409 · Accepted solution]

Hi Rajbharti,

Can you post full message log?

Regards,

Khushboo

[Former Member · Accepted solution]

Yes Khusboo,

Please check below i have maintained full message log:

[JuergenPitz · Accepted solution]

Hi,

you need to show the log of the ppf action, then you can probably see what the issue is. But the probably issue is written by Suraj already: "I can see your IDN does not have ASN no and that is one of the required entry for ID to be created.".

It depends on your EWM release. But the ASN must be unique for every delivery from one vendor (that is the standard setting). In older releases a blank was also interpreted and could not be used a second time, but if you have not changed the setting, at least a second use of an ASN leads to this error. Can you compare the ASN with other deliveries?

Brgds

Juergen

[former_member804409 · Accepted solution]

Juergen,

Just curious to know is ASN a mandatory field? I am working on SCM 9.1 and I have many test cases where I did not enter ASN but it never failed(multiple cases of blank ASN with same vendor).

[former_member804409 · Accepted solution]

Hello Rajbharti,

.For your IDN can you go to PPF action tab ,select action details and then select log.?Post that log here.

Regards,

Khushboo

[JuergenPitz · Accepted solution]

Hi,

no, it is not a mandatory field. As I described, the system checks the uniqueness. And it used to have an issue with a second "blank" as well. But since 7.x this has been changed. A blank is not creating an issue (and I usually also leave the field empty).

Brgds

Juergen

[former_member804409 · Accepted solution]

Thanks for the clarification Juergen

[Former Member · Accepted solution]

Hi Khusboo,

Thanks for the below explanation.Please find the log may this help us:

[Former Member · Accepted solution]

Hello Juergen,

I am using EWM 7.x series , so i need to maintain the ASN no?Please check the below log:

[Former Member · Accepted solution]

Hello Rajbharati

Kindly check the information in /SPE/OL19  and See the Blue information it should be appear with some information. Also, if possible delete and recreate the Logical System and Queue Types as:-

SCM Basis → Integration → Basic Settings for Creating the System Landscape → Assign Logical System and Queue Type

and create the Inbound delivery and transfer.

Thanks

Yogesh

[former_member804409 · Accepted solution]

Rajbharti,

In IDN,PPF action tab at item level go here and post log .Also since you are using an older version it could be because of blank entry but you should get more details in the log .

[Former Member · Accepted solution]

Hello Khusboo,

Thanks for the above details.Please check this as you suggest:

[Former Member · Accepted solution]

Hi Yogesh,

I am not aware of the /SPE/OL19.Could you explain what it is?

SCM Basis → Integration → Basic Settings for Creating the System Landscape → Assign Logical System and Queue Type

While for above steps may i ask Basis team to do the same?

Thanks

Rgds,

Bharti

[former_member804409 · Accepted solution]

Rajbharti,your log doesn't give much details. Are you working on test system?Dis you check as per Suraj's suggestion if you already had delivery with blank ASN before creating this one?

[Former Member · Accepted solution]

Hi

No, it is production system.I don t know why the info is limited here.

Thanks

Regards,

Bharti