Container Management after Splitting an SFC into two.

[Former Member]

Hello all,

I created a scenario in which a Shop Order was released with Lot size 3. A single SFC(SFC_1) was generated and processed.  And later attached to a Container with Carrier ID (say CONT1) and the container was closed for subsequent operations.

After processing on two operations, the container was opened.
SFC was split into 2, and I tried to repack this child SFC( SFC_1_child) into another container with a different ID (say CONT2). This container already had an SFC (SFC_2) packed into it. So i reopened the container. And added this new split SFC( SFC_1_child) with Qty 1.

But now while retriving the container(CONT2) details from Pack/Unpack Activity in ME 6.0,

I keep on getting an error, Wrong Packing Level value, and cannot see any SFC.

But the database table shows both the SFCs(SFC_2 and SFC_1_child) packed into CONT2 with Status 'Open' with Qty as 3&1 respectively.

Please help.

Regards.

[alexander_teslyuk · Accepted solution]

Hello

According to SAP Note 1266247 you can only add into this container SFCs which were unpacked from it. You can not add new SFCs to it.

Please, let us know if you have ME version where the constraint relaxed.

Regards,

Alex.

Message was edited by: Alexander Teslyuk

[Former Member]

Hi Alex and Konstantine,

I am using SAP ME 6.0.3.3

According to SAP Note#1266247,

This constraint was relaxed in:

- ME 5.2: SP07 and higher;

- ME 6.0: SP04 and higher.

So, this means I would need a ME 6.0.4 version to curb this issue?

Also, the note says,

So if you pack SFCs 1,2,3,4 close the container and remember that it was supposed to be 1,2,3 and 5 - what you have to do is unpack 1,2,3,4 and then start a totally new container and pack 1,2,3 and 5 into it.

In my case, I tried packing SFC 5 into a container. It showed me a Wrong Packing Level Member error. Then why does it update the database table with the SFC shown added to the container? And doesn't allow me to pack this SFC into a new container at all.

I am attaching two screenshots for your reference.

Pls help.

Regards,
Saayandeepa

[former_member182330]

Saayandeepa,

You are correct - it's better to upgrade to the latest patch of SP04 and retest there. If you still see inconsistencies - then it's a good reason for submitting a support ticket. It's hard to say exactly what happens behind the scenes in DB, it could definitely be some sort of a bug in the way container-SFC mapping data is stored.

Regards,

Konstantin

[former_member182330]

Saayandeepa,

According to the note provided by Alex this restriction was removed starting from ME 5.2.7 and 6.0.4. Thus if you still see such behavior in the latest releases, I would recommend to submit a support ticket for investigation.

Regards,

Konstantin