Skip to Content
0

In EWM API, Is it possible to post GR and put away without a HU?

Apr 24, 2017 at 11:22 AM

244

avatar image

Hi all,

When using the Advanced Production Integration (API) functionality in EWM, we can post GR of a HU based on the EGR from ECC.

However, is it also possible to post the GR for a manufacturing order without a HU?

Many thanks in advance!

Zain

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Juergen Pitz
Apr 25, 2017 at 06:19 AM
0

Hi,

of course you can also receive materials from production without an HU. Just this specific function (https://help.sap.com/saphelp_ewm94/helpdata/en/ad/aceb535cbb5d1ee10000000a441470/frameset.htm) which creates the inbound delivery in the background is based on HU. But when working with expected goods receipt documents you can create the inbound delivery also without HU.

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

WM->EWM migration workshop: https://blogs.sap.com/2017/03/22/neuer-migrationsworkshop-fur-sap-ewm/?source=email-de-education-newsletter-20170331&lf1=6491587571f559927336887a71904358

Share
10 |10000 characters needed characters left characters exceeded
Zain Alneame Apr 26, 2017 at 08:11 AM
0

Hi Juergen,

Thanks for your quick reply!! Obviously I will ask the follow-up question ;) How can we achieve the GR of a batch on PMR? In the standard functionality, the RF only supports the GR of HU on Manufacturing order.

Many thanks in advance!

Zain

Share
10 |10000 characters needed characters left characters exceeded
Zain Alneame Apr 26, 2017 at 08:42 AM
0

Some more background information; at the moment we are using HU-managed finished products, and want to receive batch managed by-products (therefore two items within the same EGR doc).

As mentioned, for receiving HUs on a PMR, we use the RF functionality that will create an Inbound Del in the background (works great). For receiving batches I am now looking into transaction /SCWM/GRPI. Do you know how this transaction is used in comparison with the receipt of HUs via RF? Can this transaction be scheduled in the background/PPF so that we can handle the receipt of batches only in RF?

In the case of using /SCWM/GRPI, I can create an IBD manually based on the EGR (so that I can create WOs to be processed further by the RF). Because we already handle the finished products via RF, we only want to create an inbound delivery for the by-product items and not for the finished product. However, we are not able to distinguish between the two EGR items (finished vs by-products). Any idea if that is possible?


Many thanks!

Zain

Share
10 |10000 characters needed characters left characters exceeded
Srinivasa raghavan Krishnan Jun 02, 2017 at 08:57 AM
0

Hi

We cant create GR without HU why because if we do GR without HU it will not be tractable.

When we creating HU we will include storage bins and storage locations.

Better to create HU before posting GR so that good will be tractable and process will gets complete .

Share
10 |10000 characters needed characters left characters exceeded
Juergen Pitz
Jun 06, 2017 at 07:49 AM
0

Hi,

"For receiving batches I am now looking into transaction /SCWM/GRPI."

OK, this is like the "classic" transaction when working with expected goods receipt. The possibility to create the inbound delivery through RF, came only later.

"Can this transaction be scheduled in the background/PPF so that we can handle the receipt of batches only in RF?"

Not to my knowledge. And it does not make much sense. Because the idea is to create the inbound delivery once you have the material before you (or when the truck is there).

"Because we already handle the finished products via RF, we only want to create an inbound delivery for the by-product items and not for the finished product."

OK, that is fine. I guess this is the item which is NOT in an HU and that is why it does not work with RF?

"However, we are not able to distinguish between the two EGR items (finished vs by-products). Any idea if that is possible?"

??? Sorry, but you see the materials on the left side of the screen, don't you? So you select the material which you have before you and create the inbound delivery for it. Where is the problem in that? Yes, the EGR document does not distinguish it, but I still don't understand the issue.

Brgds

Juergen

Share
10 |10000 characters needed characters left characters exceeded
Zain Alneame Jun 12, 2017 at 09:13 AM
0

Hi Juergen, Srinivasa,

Thanks for your honest and clear replies!

These by-products at the current business are usually scrap metals or other products and are less valuable, therefore tracebility on batch level for these products suffices. These products are not received on pallets but in bags or boxes of irregular quantities. Therefore, the business wanted to receive them using batch numbers (=as-is way of working). Furthermore they only have a RF scanner at that location.

- "OK, that is fine. I guess this is the item which is NOT in an HU and that is why it does not work with RF?"

for EWM API that is true.

- "??? Sorry, but you see the materials on the left side of the screen, don't you? So you select the material which you have before you and create the inbound delivery for it. Where is the problem in that? Yes, the EGR document does not distinguish it, but I still don't understand the issue."

The issue is that using the GR from production via the RF is very convenient for the business. If they used this transaction (GRPI), then they required more manual handlings and also a terminal. We wanted to automate this process as much as possible, but for that we had to differentiate between the items.

To ensure the least complexity and least manual work, we convinced the business to use HUs instead for all GRs from production and therefore this issue was resolved.


Thanks again for all your help and for thinking with us! Kind regards,

Zain

Share
10 |10000 characters needed characters left characters exceeded