on 06-25-2013 3:00 PM
Hi,
We have PO created with account assignment N and a generic storage location. During GR the storage location is not displayed in the MIGO screen (rightly so) as it is direct consumption against a network. But my problem is this:
When I do a GR label print (WEE1) the system does not print the the labels. There are no documents to select in MB90. Also the 'individual slip' is defaulted in create PO screen, but after GR when i go into the purchase order history and click on the material document it does not show the 'individual slip' (i have NDR=X)
My condition type in MN21 has storage location as a mandatory field, how can I make this as an optional field which will enable me to create condition records withou storage location.
PS: when i did a debug of the system it returned storage location as initial and exited the transaction without creating the GR label.
Thanks,
Deepak.
Hi Deepak,
There is nothing wrong with the system. As you already aware that Account Assignment Category 'N' posts to consumption, so there is no role for the storage location here. Since storage location is not passed to the communication structure, system cannot determine the output type.
To get the GR slip for consumption posting, first create a new table (for example 900) by copying your existing table for the GR slip and remove the storage location field.
And then go to NACE -> Access Sequence -> 0001 (assuming you are using the standard access sequence) -> Accesses and add one more sequence in the bottom with the new table 900.
Once you added the new sequence, make sure that 'Exclusive' indicator is ticked for the previous table. Otherwise it will generate 2 outputs for stock posting GR's. After this setup, while creating condition record in MN21, Choose the new access sequence without storage location and create condition records for the relevant plants.
Regards,
Asik.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Deepak,
Alternatively, I just noticed that there is an option available to enter the blank storage location in the condition records by enabling the 'Initial Value Allowed' indicator in the table of the Access Sequence (Path: NACE -> Access Sequence -> Access -> Fields). Just enable this for your existing table with storage location field and maintain the condition record with blank storage location.
By the way, the option of creating the new table without storage location also should work. To analyse further, please provide the Access sequence and condition record details of the new one.
Regards,
Asik.
Hi Deepak,
Before going forward with the option of creating new table, did you try the below option mentioned in previous reply?
"There is an option available to enter the blank storage location in the condition records by enabling the 'Initial Value Allowed' indicator in the table of the Access Sequence (Path: NACE -> Access Sequence -> Access -> Fields). Just enable this for your existing table with storage location field and maintain the condition record with blank storage location."
Regards,
Asik.
Hi Deepak,
Recheck the followings
1. Check is there any Requirement Routine in NACE-ME-Access Sequence-Z001-Accesses-900(table). If any routine is assigned, remove it
2. In the condition record, make sure that Trans./Event Type is 'WE', Print version is 1 and Dispatch time is '3' and Output Device (Printer) is assigned
3. In MIGO-General, check Print option is ticked and Individual Slip (Print version 1) is selected
4. After completing the transaction, please check Output tab - Messages is appearing in MIGO item level
If nothing works, please provide screen shots of Access Sequence and condition record.
Regards,
Asik.
Hi Asik,
I created a new access sequence and a new table in sandbox and changed the output type WEE1-ME to include the new access sequence. It worked fine. But when I replicated these same changes in development, it did not work for some reason.
So in dev I did not create an access sequence but created a new table and assigned it to the existing access sequence and based on your suggestion marked the old table "exlusive". It worked fine in dev and so I transported that into prod.
Thanks,
Deepak.
User | Count |
---|---|
99 | |
8 | |
6 | |
6 | |
5 | |
4 | |
3 | |
2 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.