Hi,
There is no direct option in standard as of my knowledge. However, you may add your own field in the field catalog of MB51 through development, as explained in the note: 357187 - MB51: Fields in field catalog / selection screen
Regards,
AKPT
↧
Re: Plant Desciption/Vendor Part No. required for MB51 / Need to export MB5B & MB51 Reports to Excel
↧
Re: MC.1 Report Showing different data every time it is executed
Hi,
In addition, I would suggest to rebuild the S032 , S031 & S039 info tables in OLIX as explained in the KBA: 1858368 - Value for field “Valuated stock” or “ValStockValue ” is incorrect in S032 and check the scenario again.
Regards,
AKPT
↧
↧
Re: Return to Vendor 161 with outbound delivery
Hello,
I have read this post and after spending a few hours trying to understand this process I have determined the correct process and would like to post that here for any one who is in the same spot as I was.
for the reverse logistics scenario of store to DC you cannot use a purchase order (document type NB) and use return delivery RL. i was using this process and ran into the same error as described above. Since you cannot add in a new value within movement types since L is missing from configuration that should lead you to believe that you have done something incorrectly. Doing more research and following the help text within the IMG you must leverage the NLR (or NCR) return delivery type. This will allow you to create a Stock Transport Order with the return indicator and ultimately allow you to create a delivery with movement type 671.
The trick is the order you must perform is Stock Transport order creation using ME21N
Create the delivery against that stock transport order (delivery order type NLR or NCR)
Perform a goods receipt against that Stock Transport order first (movement type 161)
this will place the goods in transit you can use MB5L to see your goods.
Then perform the goods receipt against your delivery order (NLR) (movement type 671).
Goods will be removed from in transit to the destination DC.
Please refer to the help portal link as follows
and the SAP note 430074 for more details around this standard scenario.
↧
Re: New Payment block need to picked in MIRO instead of R
Hi,
Do you have blocked indicator Q in your system?
Generally blocked indicators are as *, A,B,I,N, P, R and V.
I believe development already considered to block invoice posting if material is in quality inspection by showing an error message during invoice posting for your purchase order in MIRO- now what is your new expectation. Just cross check requirement and look system design possibility for your expectation.
Regards,
Biju K
↧
Partner Segment Field during MIGO
Hi,
There is a FI Validation for GL A/C 100000 to have Partner Segment field (PSEGMENT) mandatory.
There is PO with account assignment K for GL A/C 100000.
During MIGO posting, the validation error prompted to have the Partner Segment field to be filled.
We could not find Partner Segment field in MIGO screen.
OME9 does not have that field either. Is there a workaround to this?
↧
↧
Re: VMI: creation of PO for vendor
Hi, sorry, what do you mean with the action code? I have an IDOC of type ORDRSP.
Best regards
↧
Re: Atp check for special stock M(returnable packaging parts Vendor)
Please note
1. You cannot create PO for RTP material. Only do GR as Non Ordered Item (501+M) for PO
2. RTP belongs to a Vendor
3. MRP/ATP will not consider Special Stock M
4. You cannot sell RTP
Regards,
Niranjan
↧
Re: Jurisd. Code at PO Item Level not triggering any validations
Phani,
Review through the transaction OBCO, where you "Specify Structure for Tax Jurisdiction Code", associating the calculation scheme used with the structure of jurisdiction code.
↧
Re: VMI: creation of PO for vendor
OK got it. Action is 004 in segment E1EDK01
↧
↧
Re: Specify Jurisdiction Key MIRO GL Tab
Hi,
May be your purchase order created with sales order which in turn you find in MIRO screen.
Now cross check tax jurisdiction code is available in your plant( for which your Purchase Order Created) in t.code: OX10, If not maintained- just maintain it and save for your plant.
Now create new a PO with your sales order and carry out MIRO to find how tax jurisdiction code appears in MIRO screen!
Regards,
Biju K
↧
Re: Atp check for special stock M(returnable packaging parts Vendor)
Dear Niranjan,
Is it possible to crate a PO for RTP material with Free of Charge in ME21n?
↧
Goods movement inconsistent status in Outbound Delivery
Hi SAP SD Experts,
I have one outbound delivery and its PGI was done. However, the GI material document was archived (thought I did not know why or who did that). The status of Goods Movement is still shown as Completed and I cannot reverse the PGI.
Here is the screenshots for your reference. I would be grateful if you can advise me solutions to sort it out.
Thanks in advance,
Regards,
Danny
↧
Re: T-Code for Material ABC Analysis for Items with movement 201/202 only
Hi,
Standard reports and consumption tables are updated based on the consumption indicator in the movement type. You may check the same in OMJJ.
Also check the notes: 1832196 and 804011 which provides additional information.
If you want the consumption posting to be same and ABC analysis to be taken only for 201, you may go for a custom report!
Regards,
AKPT
↧
↧
Re: Jurisd. Code at PO Item Level not triggering any validations
Hi,
Did you entered tax jurisdiction code for your plant (plant for which purchase order created) in t.code OX10, If not maintained- Just maintain fro your plant and save.
Now try creating a new purchase order and carry out invoice verification for your purchase order to find how tax jurisdiction code behaving!
Regards,
Biju K
↧
Re: VMI: creation of PO for vendor
ORDERSP is only for Order Change. Use ORDERS05 for PO creation. Check Documentation in WE60. You need org data like purchasing org, company code which is possible in ORDERS05.
Regards,
Niranjan
↧
Re: MEMASSPO does not support upload of manual pricing condition
Hi,
Before updating value in purchase order condition type by any tools- better check design details of your condition type in t.code: M/06 where change allowed or not ,once purchase order created!
Regards,
Biju K
↧
Re: MEMASSPO does not support upload of manual pricing condition
The question was not just for value. It was for both condition type & value. These are manual conditions that do not appear in the PO without the user adding it.
↧
↧
Re: MEMASSPO does not support upload of manual pricing condition
Hi,
Check Condition type design and setting in t.code M/06. Based design - system allowed condition type should be appears in purchase order automatically or manual entry possible for condition type in purchase order. Cross check "Changes which can be made" segment for your condition type which play vital role for your requirement and cause your concern!
Regards,
Biju K
↧
Re: Condition Records report
Hi,
Please check the document: Pricing Report in MM which explains the standard report option!
Regards,
AKPT
↧
Re: Condition Records report
Hi,
You can refer condition record in t.code: MEK3 but for details with all condition types, refer
Regards,
Biju K
↧