on 11-28-2016 8:47 AM
Hi,
I set STO intercompagny as per SAP requirements and it is working fine.
However, I'm facing issues to process return STO.
In my example : plant 1000 is assigned to a vendor (supplying plant) and plant 1010 is receiving plant. Now for quality reasons I have to return material from plant 1010 to plant 1000.
When I try to perform return, I create a new STO pruchase order and use the flag "Return". I have my tab "shipping" with customer representing supplying plant and correct delivery type (NCR).
I create delivery through VL10B and when I try to post GI, I get the following message : "Purchase order 4500000XXX has different supplying plant 1010". I guess the system is reading the supplying plant as in the STO process.
I can't find any proper information about the configuration of return STO process in the existing threads.
Could someone please guide me through this process ??
Thanks
Kevin
There are not much options, you either find the coding that affects the program logic to keep using the SAP standard return process, or you alternatively just do the business in reverse with a normal STO.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jürgen,
Thanks for your help. I had a look with an ABAPer and he saw that the correct plant was read before a redetermination of the plant in the supplier (supplying plant) but he has no more clue. He also checked that there were a lot of existing enhancements.
From your knowledge, what would be the best scenario for a return STO knowing that I should stick to SAP standard ?
Kevin
,Jürgen,
Thanks for your help. I had a look with an ABAPer and he saw that the correct plant was read before a redetermination of the plant in the supplier (supplying plant) but he has no more clue. He also checked that there were a lot of existing enhancements.
From your knowledge, what would be the best scenario for a return STO knowing that I should stick to SAP standard ?
Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you have to contact an ABAPer now who can debug to see which values the fields have when the error message is triggered.
It can be a side effect of own coding in user exit.
You can also try to analyze it via transaction ANST (is able to show you your own developments) and PANKS which can search for OSS notes based on the error message
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jürgen,
Find enclosed a screenshot of SE16N : EKKO-RESWK
As you can notice, value of supplying plant is the same which make sense as the system is picking the plant assigned to the vendor. Though, I can't understand how I can tell the system (other than the "return" indicator) that the issuing plant is not the initial supplying plant.
Kevinse16n-ekko-reswk.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
okay, same vendor in both PO. So far I can only imagine that the vendor plant assignment got changed between PO and return PO.
Can you check on table EKKO with SE16 to compare the values of field RESWK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you post screenshots from the original PO and your return, so that we can see the supplying plant.
If I do a where used search for error message ME723 then I just get to this piece of code:
*- Lesen Bestellkopf, prüfen ob Umlagerung vorliegt -------------------
IF ekko-reswk NE reswk AND
reswk NE space.
MESSAGE e723 WITH ekko-ebeln ekko-reswk
RAISING wrong_delivery_plant.
ENDIF.
There is not really much in this code than just comparing the values of the supplying plant field EKKO-RESWK with your entered supplying plant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.