Hello Jinoy,
Definitely, there could be some OSS notes available for this. We have to spend sometime and search the OSS Notes for this. Since this is available in next version and not in 7.0. So, SAP might have released some OSS notes for lower versions to support the same function. I will search few and let you know, If I find anything relevant to this.
Regards,
Sathish
Hello all,
We have an issue for 2 different clients in the very same adress: Both have the same unloading point in the same route, but materials cannot be packed in the same HU.
Client 1 - Distribution Route A, unloading point 1
Client 2 - Distribution Route A, unloading point 1
If try to repack 2 items in an HU, we get error message: "different clients cannot be repacked in the same HU". What we are doing now is to create 2 diferent HU, one for each and then palletize both in a multi-customer HU.
Where can this option be trigered: 1 HU (not palletized) for 2 different clients
Thanks!
Hi,
you can find sample questions here: https://training.sap.com/shop/certification/c_ewm_90-sap-certified-application-associate---extended-warehouse-management…
Pls do not ask others for questions...
Brgds
Juergen
Dear Sathish ,
Thanks for your support .
Jinoy
Hi Walter - can you please share the code used in BADI implementation to populate table /sapapo/matlwh?
Regards,
Rama Krishna.
Hi there,
LOOP AT lt_sc_unit INTO ls_sc_unit.
CLEAR: ls_matlwh, ls_matlwhx.
* Vullen en toevoegen van structuur ext_matlwh (tabel /SAPAPO/MATLWH)
* Verplichte velden tbv. correcte verwerking
ls_matlwh-method = ls_sc_unit-upd_code_matlwh.
ls_matlwh-ext_matnr = lv_extmatnr.
ls_matlwh-ext_entity = ls_sc_unit-scguid_ext.
ls_matlwh-scutype = '1001'.
ls_matlwh-ext_entitled = ls_sc_unit-entitled.
ls_matlwh-ptdetind = '01'.
ls_matlwh-put_stra = '0001'.
ls_matlwh-ccind = 'C'.
APPEND ls_matlwh TO lt_matlwh.
* Verplichte velden tbv. correcte verwerking
ls_matlwhx-method = ls_sc_unit-upd_code_matlwh.
ls_matlwhx-ext_matnr = lv_extmatnr.
ls_matlwhx-ext_entity = ls_sc_unit-scguid_ext.
ls_matlwhx-scutype = '1001'.
ls_matlwhx-ext_entitled = ls_sc_unit-entitled.
* Data-velden / scherm-velden
ls_matlwhx-ptdetind = 'X'.
ls_matlwhx-put_stra = 'X'.
ls_matlwhx-ccind = 'X'.
APPEND ls_matlwhx TO lt_matlwhx.
* Vullen en toevoegen van structuur ext_matlwhst (tabel /SAPAPO/MATLWHST)
* Verplichte velden tbv. correcte verwerking
CLEAR: ls_matlwhst, ls_matlwhstx.
ls_matlwhst-method = ls_sc_unit-upd_code_matlwhst.
ls_matlwhst-ext_matnr = lv_extmatnr.
ls_matlwhst-ext_entity = ls_sc_unit-scguid_ext.
ls_matlwhst-scutype = '1001'.
ls_matlwhst-ext_entitled = ls_sc_unit-entitled.
* Data-velden / scherm-velden
ls_matlwhst-lgtyp = '0001'.
APPEND ls_matlwhst TO lt_matlwhst.
ls_matlwhstx-method = ls_sc_unit-upd_code_matlwhst.
ls_matlwhstx-ext_matnr = lv_extmatnr.
ls_matlwhstx-ext_entity = ls_sc_unit-scguid_ext.
ls_matlwhstx-scutype = '1001'.
ls_matlwhstx-ext_entitled = ls_sc_unit-entitled.
* Data-velden / scherm-velden
ls_matlwhstx-lgtyp = 'X'.
APPEND ls_matlwhstx TO lt_matlwhstx.
ENDLOOP.
* Schrijf de gevulde structuren weg tbv. de verwerking
et_matlwh = lt_matlwh.
et_matlwhx = lt_matlwhx.
et_matlwhst = lt_matlwhst.
et_matlwhstx = lt_matlwhstx.
Hello Uta,
Just want to check with you have you resolved the issue? We also don't want to use liveCache for our install for EWM.
Please let us know the workaround to bypass the livecache install and thanks in advance.
Sunil
Hi, Greetings.
Thanks for your quick response.
Please let me know what the below variables are in your code?
lt_sc_unit
lv_extmatnr
for now i have imported it_matkey, but i get an error : System D15CLNT300 not assigned to any business system. (D15CLNT300 is source system and i am getting this error in target system)
Please assist.
Regards,
Rama Krishna.
Hi Walter - I am implementing this BADI to insert data into /sapapo/matlwh, so i wouldn't find any rows.
Regards,
Rama Krishna.
Dear juergen ,
Kindly guide me as how to activate log for checking same , filter rule is created and assigned respectively.
Below screen shot for your reference.
Hello Jinoy,
use tcode /scwm/actlog and activate the log and post the log
Jobi
Hi,
/scwm/actlog is not enough... Here you have to activate the log for the objects you want to control.
For a WOCR you additionally need to activate the details in /SCMW/WOLOG. And then you either use transaction SLG1 or (easier to find) use the "Other Methods" on the warehouse order to see the log.
Brgds
Juergen
Hi Walter,
I personnely beliveve that SAP is process driven rather technology driven.
I would like to understand why do you want to create warehouse products from CIF?
Once the product is maintained this is extended to eWM to maintain additional master data of eWM. If you CIF the data you are getting only ERP data from the system.
by the way I am not moderator..
Regards
Sastry
Hello Sastry,
I cannot answer that question exactly, because it was a requirement of the customer...
Like you say: If you CIF the data you are getting only ERP data from the system.
So obviously, the warehouse product-data is missing, but according to the spec's it is required.
( I do not know which eWM process uses the warehouse product-data...)
So to save some time doing Master Data maintenance in eWM afterwards, this option of extending the CIF-interface was chosen..
Btw., there are a lot SCN-forums discussing this subject, so this is a 'common'' requirement.
reg., Walter.
Dear Jobi , Juergen
Thanks a lot for your kind cooperation.
Please refer below screen shots
Hi,
this is not the correct log, this is all PPF. Maybe it was also not clear from the previous mail, but of course this only works for WOs you create AFTER the acitvation of the log.
So you need to cancel the existing WO, create a new WT. Then the easiest way to get the log is to look for the WT in the warehouse management monitor, mark the WO, open the drop down for "other methods". Select WO creation log (or something like that...).
Juergen
Hi,
I am not sure if you really need to change this... The logical system is to find the RFC destination... All you need to do is to "bend" the RFC connection to the right destination... Not something we would recommend for DEV-QAS-PROD landscapes, but long time practice in our training systems...
Brgds
Juergen
Hi Walter - thanks for your inputs. can you please share the code for lt_sc_unit ?
Regards,
Rama Krishna.
Hi Jinoy,
At warehouse process type you are determining the WOCR - HU01.
Item filter is HU01. The warehouse task is not passed the filter following default rule has been taken.
Solution:
In the WOCR rule filer HU01 change the value of Complete HU from "only full pallet with drwals" to no restrictions.
Regards
Sastry
Dear Ramakrishna ,
Please refer below changes as suggested , but still it remains same.
Thanks
Jinoy