Quantcast
Channel: SCN: Message List - SAP Extended Warehouse Management (SAP EWM)
Viewing all 5578 articles
Browse latest View live

Re: Initial Stock Upload for Nested HUs

$
0
0

Hi,

for starters...

- in the first line the column PARENTHUIDENT stays empty (like it says in documentation).

- if the second line is the lower level HU, it can not have the same HU numbers. And it does not make any sense to the have same packaging material.

- in the third and fourth line you do not enter any packaging material (also, like it says in the documentation).

- and how could line 3 and 4 refer to ANOTHER HU number?

Brgds

Juergen


Re: Initial Stock Upload for Nested HUs

$
0
0

I have never tried such a combination included aux. pack material, and not all the information in the documentation is clear to me, but I suppose this should look something like this (see screenshot).

I assumed your outer packing is HU Type E1 and pack.material 50, the inner HU is HU type K1 and pack.material 51. I am not sure about the HUIDENT entry required for the aux. pack material (pos type 3) and if then the x for EXTNO is required. And I did not use your long HU numbers.

Brgds

Juergen

2015-12-29_14-31-31.png

IBGI not getting triggered immediately after OD creation

$
0
0

Hi

 

System is not generating the IBGI(in ECC) immediately after OD creation even though doc type settings are set for this to happen.

But please note that the HU information is getting updated on outbound delivery in ECC.

12-29-2015 6-14-03 PM.jpg

Please note that when I set the Billing Req.Ty to "B Billing Document on Request" system is generating invoice in ECC.

So I believe all the pre-requisite settings are in place. But to mention them I did following setting in ECC & EWM. Please let me know if I missing something.

ECC:

1. Logistics Execution -> Extended Warehouse Management Integration -> Billing Settings -> Determine Invoice Before Goods Issue (IBGI) Indicator

Here I maintained IBGI relevancy as "D- Allowed but not Mandatory" for my sales document type & Sales org

2. Logistics Execution -> Transportation ->Basic Transportation Functions -> Output Control -> Define Print Profiles; Here defined a print profile ensuring that the naming convension is same as that of the profile in EWM. Also assinged application V3 to this print profile.

3. Logistics Execution -> Extended Warehouse Management Integration -> Billing Settings -> Assign Output Types and Printer to Print Profiles

Here assigned the output type with print profile defined in step-2 above

 

EWM:

1. Extended Warehouse Management -> Interfaces -> ERP Integration -> General Settings -> Set Control Parameters for ERP Version Control

here selected the option Invoice before goods issue possible.

2. Extended Warehouse Management -> Goods Issue Process -> Outbound Delivery -> Manual Settings -> Define Document Types for Outbound Delivery Process; Here in required document type of doc.cat FDO choosen option " A Billing Document Immediately"

3. Extended Warehouse Management -> Goods Issue Process -> Outbound Delivery ->Print -> Define Print Profiles for Delivery Processing

Here created a print profile whose naming convesion is same as that of the one created in ECC-step-2. Also in the print profile data defined setting for action "TRIG_INVOICE"

4. Extended Warehouse Management -> Goods Issue Process -> Outbound Delivery ->Print -> Define Print Profile Determination for Goods Issue Process

Here defined the above print profile for our Whse

Re: SAP EWM MFS or Third party WCS

$
0
0

In my experience, the deciding factor has been the additional licensing , support and ongoing maintenance costs of adding an additional WCS and not using MFS. The exception has been In cases where the WCS and equipment existed prior to EWM implementation.

 

Later.....

Re: Initial Stock Upload for Nested HUs

$
0
0

Hi Juergen

 

Let me try with your Inputs and update you the status

 

Senthil

Re: Bulk Storage with addition of stock and mixed storage

$
0
0

Hi,

Then I Move it to ERP forum and there you can get help from more experts.

 

Regards,
Claire.

Inbound Delivery- Addition to stock across multiple storage types

$
0
0

Hi All,

 

          While User creating  Putaway Warehouse task for Inbound Delivery  from Transaction  /SCWM/PRDI ,  Standard Put away Strategy looks for Addition to Existing Stock then next empty bin within the same storage type before searching the next storage type in the strategy. The requirement is to first search through each storage type for addition to existing stock and then if not found start over

at the beginning of the storage type list and search for Next Empty Bin . it should work for storage types : Bulk / Pallet/ Fixed ..

 

 

             Tried to achieve by exploring with Enhancement Spots : /SCWM/ES_CORE_PTS , but it seems not going to work  as we can not stop System to search for Empty bin and move to next storage type to search for Add to stock bin , in case if no bin found in Add to existing stock scenario for same storage type

 

 

   Please  give suggestion, how we can achieve this requirement  : through either any Configurations / ABAP Program

 

 

Thanks in Advance,

Vamsi

Re: Location tags in container yard

$
0
0

Hi Jaggi

 

Can you give what exactly you are trying to achieve?

 

Regards

Suraj


Re: Inbound Delivery- Addition to stock across multiple storage types

$
0
0

Hi Venkata

 

 

Try Sorting as you want for putaway activity and hope you can achieve same.

By this way system path will be decided for putaway and at storage type level.

 

 

Regards

Suraj

Re: Inbound Delivery- Addition to stock across multiple storage types

$
0
0

Thank you very much Suraj for your response,

 

  Yes your proposal is correct, using Sorting also we can get it.

I have checked a BADI which does this Sorting . But here I have to replicate total Logic of Standard Bin Determination first with "Add to Stock Bin" Scenario for all Storage types and then if no Bin Found , I also have to include Logic of "Empty Bin" Scenario , considering all Storage types behaviours (Bulk/Pallet/Fixed Bin)  which SAP will be doing later this BADI , in standard way to propose Bin .

 

          I am Looking for any way which will solve with Less Coding Effort and any Functional Configuration setup ..

 

 

Thanks,

vamsi

Availability Check during MIGO_TR

$
0
0

Here is the scenario:-

 

We use MIGO_TR to transfer the stock from IM managed storage location to EWM storage location. Movement 301.

MIGO_TR creates Inbound Delivery which is then processed in EWM.

 

Problem:- System allows to create Inbound Deliveries without checking existing deliveries already created by user. Result:- Total number of quantity in all inbound deliveries exceeds available quantity of material.

 

Example:- If I have stock of 100 TO & user is doing MIGO_TR of 110 TO then system gives stock deficit error message.

But if user creates multiple Inbound deliveries of 50 TO multiple times system does not check open deliveries (every time it just compare Total Qty available).

 

I have always seen availability check on outbound delivery side but is there anything relevant config in this scenario to avoid this situation.

 

Regards

Re: Location tags in container yard

$
0
0

Hi Jaggi,

 

Need more details exactly what you trying to achieve.....?

 

Regards

Anoop Singh

Re: Inbound Delivery- Addition to stock across multiple storage types

$
0
0

Hi Juergen Pitz,

 

            Thanks for reply.

            Yes, we tried assigning Storage Group also , no luck.
And storage type have Strategy Addition to Stock/Next Empty bin too.

 

Generally , SAP do Bin determination in this way :

For each Storage Type , first check any Add to stock bin available ; if no then immediately checks for

Empty Bin for same storage type. 
if nothing found here too, System does same thing for Next available storage type .

----------------------------------------------------

 

My requirement is , For example to search for  a Storage Bin among all available storage Types first with "Addition to Stock"  only , if no storage Bin found then System should check  with strategy  "Next Empty Bin"  among all available Storage types ...!

        It should be applied irrespective of  whether a Delivery , Put away doing with storage types  either one of behaviour  Bulk / Pallet /Fixed .

 

using a BADI  /SCWM/EX-CORE_PTS_SRTSQ ,  if I could replicate logic of whatever Standard does

to do Bin determination , I may solve it . But here my Concern is , almost I have to Replicate total logic of standard to Bin determination for storage behaviours Bulk/Pallet/fixed bin to make it work for my requirement.

I want to reduce this code effort , with having any other available solution .

 

 

Thanks,

Vamsi

Re: Availability Check during MIGO_TR

$
0
0

Hi C K,

 

Thanks for your reply.

 

We have checked the validations, but its of no use to control availability check. Tried creating few validation profiles along with routines but not successful.

 

We are looking for ATP check functionality usage which can be achieve via Checking Rule & Availability check combination.

 

We tried lots of permutation combination in this area too but could not succeed.

 

IS there any other way to achieve this?

 

Regards

Re: Availability Check during MIGO_TR

$
0
0

Hi,

 

Try with the below BAdi to execute the availability check.

 

/SCWM/EX_DLV_AVAIL_CHECK – Availability Check Processing of Input and Out-

put Data

 

 

C K Reddy


Understand HU & Product WT

$
0
0

Hi,

 

This is regarding the following explanation available for HU & Product WT in help.

 

HU WT: It does not reserve any quantities.

Product WT: A product WT reserves the quantities, so that these are no longer available for other product WTs.

 

Can some one throw some light how we can prove above sentences in system. I mean how can we know that product WT reserves the quantites where HU WT does not

 

BR

Raghava

Re: Understand HU & Product WT

$
0
0

Hi,

 

Here in EWM there are two kinds of WTs generated.

 

1. HU warehouse task : products can be moved in the form of HU. If an HU warehouse task is used, we can track the warehouse movements of the products associated with the HU.

 

 

2. Product warehouse task : Products can be moved on their own in the warehouse as part of a product warehouse task.

 

for process oriented storage control , HU WTs are mandatory to move the products from one proces step to other step.

 

C K Reddy

Issue in HU WT during final putaway

$
0
0

Hi,

 

I am using a POSC with following steps Unloading,deconsolidation,putaway.

 

In the final putaway storage type for putaway storage control indicator value 2- Storage Control: Putaway with Product WT is chosen.

 

With this when we putaway one material, system is creating HU WT for the final putaway. But the same is not happing when we have mixed products into single HU and getting below error during WT creation for first step.

12-31-2015 2-36-39 PM.jpg

when I further analyzed the log, as a final step of determine source data-start for some reason system did not determine the HU type which happening when we have single product.

please refer below screen shot of the above error log

12-31-2015 2-39-10 PM.jpg

Log details when single product is being putaway

12-31-2015 2-42-43 PM.jpg

 

BR

Raghava

Re: Issue in HU WT during final putaway

$
0
0

Hi,

 

check the settings in storage type under putaway control area, either it is allowing mixed products in HU 'or' not..

 

mixed HU.png

 

C K Reddy

Re: Issue in HU WT during final putaway

$
0
0

Hi,

 

Yes in Mixed storage & Mixed storage in HU, option blank is chosen indicator mixed storage w/o limitation.

 

BR

Raghava

Viewing all 5578 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>