Query Regarding LB13 Transaction

[former_member218144]

Hi All,

Currently we are using WM-PP interface for material staging.We use pick parts staging with dynamic bins.

The TR gets created during the order release.The same finished production is produced in 2 different places.

Once the TR gets created ,the warehouse user converts the TR into TO in LB13 transaction.But the warehouse team is unaware where the material needs to be sent since the requirement number of the TR is the production order number.

They need to open the Order and check for the Work center to identify the destination of the materials.

In case of fixed bins, the Requirement number is the PSA hence its easy for them to identify the destination.Is there a way to configure the requirement number to be PSA instead of the order number for dynamic bins. Also please let me know if there is any setting to add PSA in the LB13 transaction.

Regards

Richie

[DominikTylczyn · Accepted solution]

Hello Richie, LB13 is implemented by SAPML02B report. The program hosts in total 12 transactions. In order to enhance LB13 you would have to modify the program thus potentially affecting all these transaction. That is a substantial change.

Thus I can see three ways to get you the information about precise destination of a material in production supply process:

1. Use individual storage types for PSAs
2. Use individual fixed bins for PSAs in standard storage type 100
3. Use storage position field in control cycle record

Best regards

Dominik Tylczynski

[former_member218144 · Accepted solution]

Hi Dominik,

Thanks for your response. The storage position field seems to be be feasible option to my requirement.

But this field is not getting displayed in LB13 transaction.

Do we have a report for TR's which has this storage position field.

Regards

Richie

[DominikTylczyn]

As far as I know storing position should be copied to unloading point field in a transfer requirement item. At least storing position field and unloading point in TR item share the same technical name ABLAD, thus that should be copied.

Just go and try it. Unloading point should be definitely available in LB13.

Also you can maintain unloading point directly in PSA definition:

Consult the notes on the copy logic:

769827 - Unloading points are not updated in release order parts

771582 - Unloading points are not updated in release order parts, par

Cheers

Dominik Tylczynski

[former_member218144]

Hi Dominik,

The storage position is getting updated in the unloading point field in the TR.

But the unloading point field is not available in LB13 nor LB10 .

You have any suggestion on this part.

Regards

Richie

[DominikTylczyn]

Unfortunately as mentioned previously there not enhancement points in LB13 - at least not ones that I know of.

But why do you need that information in LB13? The components destination in production supply process is relevant during transfer order execution, not necessarily during TO creation.

Dominik

[former_member218144]

Hi Dominik,

The warehouse team creates the TR and the manufacturing team confirms the TO based upon the receipt.

Hence the warehouse team needs to know the destination in LB13 screen. But I realized the unloading point data can never be pulled in the LB13 screen because unloading point is at item level and LB13 data is at header level.

But I am still going ahead with your proposal of maintaining of the storage position.

Thanks for helping me out.

[DominikTylczyn]

Why don't you assign different storage types to different PSAs? This way the destination will be clearly visible on a transfer order.

BR

Dominik Tylczynski

[former_member218144]

We are using the standard storage type 100 for dynamic bins.

Adding individual storage type for each PSA is a big process change.

Hence I would like to add PSA somewhere in the LB13 screen.

Regards

Richie