STO (via EDI) extend delivery

Dear, colleagues
Our customer has requested to setup Intercompany Stock transfer Orders to supply sales stores form DC. Business scenario is:
- Store creates PO for goods
- DC creates Delivery documents based on PO (vl10b)
- Goods are delivered on Pallets, each store takes care about them. There are no PAL in PO doc, DC add then only in at the moment of delivering (in delivery doc).
- Goods issue/ receipt
- Intercompany billing
- Invoice verification
The problem I faced is what to do with PAL in IV? In fact, I have to process them as normal goods. It seems to IV has to be created on Goods receipt base, unfortunately SAP threats PAL as extra costs, not as goods
Does anybody has faced with such scenario?
Many thanks
Valters
To make live interesting, ICB stuff should be done via EDI

You do not need to use EDI messages to get an inbound delivery created when a PGI is done on the outbound delivery.
Search for the config on the SPED output type. This SPED output message can be triggered during the PGI which results in the creation of an inbound delivery in the receiving plant.
The receiving plant will have to maintain the confirmation control key 0004 at item level in the purchasing document.
Link to SAP help Automatic Creation of Inbound Delivery - Transfer and Inventory Management - SAP Library
Refer SAP note 1119073 point 3 and note 965176
Regards,

Similar Messages

Inbound delivery creation in STO via EDI/Idoc

Hello experts,
My requirement is like this:-
Stock transfer order is created for supplying plant 2000 & receiving plant 2010.
When the supplying plant 2000 posts an outbound delivery & PGI, at same time an Inbound delivery should be created in receiving plant 2010.
I know theoretically that this is achieved by making confirmation settings & output types. But don't know exactly how to configure it.
Can you please mention the process?
I have referred the scn threads:
Outbound Delivery to Inbound delivery by using IDOC
how to configure the message control for DESADV
SAP note 111903
Receiving Vendor Confirmations via EDI - Purchasing (MM-PUR) - SAP Library
But there is lack of clarity from my side.

You do not need to use EDI messages to get an inbound delivery created when a PGI is done on the outbound delivery.
Search for the config on the SPED output type. This SPED output message can be triggered during the PGI which results in the creation of an inbound delivery in the receiving plant.
The receiving plant will have to maintain the confirmation control key 0004 at item level in the purchasing document.
Link to SAP help Automatic Creation of Inbound Delivery - Transfer and Inventory Management - SAP Library
Refer SAP note 1119073 point 3 and note 965176
Regards,

Update "Delivery Completed" Indicator in PO Item via EDI

Hello
We have another challenging task regarding purchase order confirmations that we would like to tackle (SAP Release is ERP 6.0).
The 2 partner in our scenario are distribution companies (= DC) which order goods and production companies (= PC) which deliver the goods:
(1) DC sends purchase oder via EDI (ORDERS IDoc)
    -> creates sales order in ERP of PC
(2) PC splits sales order into multiple deliveries.
   Each delivery is sent as outbound DESADV
   -> creates inbound delivery in ERP of DC.
(3) At some point the PC has completed the sales order
   yet it is possible that less was delivered than was ordered
      (i.e. we can have under-deliveries).
Now the question is:
How can the PC transmit the final information "SalesOrder completed" implying that the "Delivery Completed" indicator in the PO items should be updated (= 'X')?
My assumption is that we need to look at the sales order (ERP of PC) because this is the document which "collects" the information from all the split deliveries.
Any help related to understanding how the (standard) business process would look like and how to translate this into a technical solution (EDI / IDoc) is more than welcome.
Regards
Uwe

Hello Uwe,
As you mentioned, I tried to check with the Workflow solution by tracking the events through Business Object BUS2032 (Order) or LIKP (Outbound Delivery) but failed to get successful results.
Problem with BUS2032, event CHANGED is that it doesn't get triggered when the Header/Item level status changed during delivery Processing.
While using BO- LIKP (Outbound Delivery Processing), Events - Changed,Created, I am successful in triggering the event, but the problem with BO-LIKP is that, it does not have the item level details in the ATTRIBUTES list. To get the balance quantity available for order line item (mentioned in my earlier reply)Item details are necessary to findout the Reference Sales Order & Line item. With this, the Option of Triggering of Workflow using LIKP didn't give the required result.

How to skip the Inbound Delivery while updating LA confirmations via EDI

Hi Experts,
I have a requirement wherein I dont want to create Inbound Delivery automatically when updating the LA (or a copied Conf Cat of LA) confirmation via EDI. When we are using the message type DESADV, LA confirmations are being updated, but simultaneously, the Inbound delivery also being created. My client desires that Inbound Delivery should not happen and only LA confirmation should be updated via EDI.
Is there anyway, by which we can skip the Inbound Delivery while updating the LA confirmations in the PO?
Thanks in advance
Regards
Radha Krishna

Hi Prabhaharan,
Thanks for your quick response.
My requirement is to have both AB and LA confirmations. I have included these two in a new the conf control So, your suggestion will not work.
Is there any other way out to fulfill my requirement?
Thanks & Regards
Radha Krishna

DELIVERY BLOCK AT HEADER LEVEL FOR ORDERS VIA EDI...

Hi Experts,
I have got a situation, My client gets an EDI inbound sales orders from Canada, for those orders he faces delivery block at header level..which they dont want...
Can someone please guide me exactly where he receives those orders, how he processes it, and whats the background configuration for bloking those orders...how to start the checking the settings
Thanks & Regards,
Srikanth.R

Hi,
Get the posted Sales order number # via EDI ie We02. Now got to VA03 and input that sales order.When the sales order is opened.
Now from the Menu -->Go to >header>Sales .Note down the order type.
Now go to the Transaction code:VOV8 for the order type check whether the delivery block is maintained.
Regards,

Exit for delivery Date check in Sales order [Via EDI]

Hi Friends ,
We have a requirement in which if the Sales Order is created Via EDI with INVALID delivery date then I have to set a flag in some Z Table . I have tried searching for exits and debugging the code but was unable to find a place where SAP checks for delivery date validity . Please help me with possible exits/Badis?Enhancement Pts etc where I can mark this flag .
Thanks & Regards
Gaurav Deep

@Vinod Thanks for your reply , the delivery date is there in EXIT_SAPLVEDA_009 .
But how will i check if the delivery date is valid or not , If you go to VA01 and give a invalid delivery date a warning message is issued , here if the warning message is issued then I want to set my flag , this might save my from coding redundant delivery date check logic , can someone please help me how can i track if this warning message is issued .
Thanks & Regards
Gaurav Deep

Send Vendor Invoice Via EDI

I have a request to setup our system so that whenever an invoice is posted against a particular vendor an IDOC (of the invoice) is generated and sent via EDI to this vendor. What steps do I need to take to make this happen?
I have created a partner profile, with an outbound parameter of an invoice message type. However, when I post an invoice (MIRO) against this partner no IDOC is generated.
Thanks - points will be rewarded.
Edited by: Brian M Swanson on Feb 7, 2008 10:19 AM

You can use Idoc message type DESADV to get confirmations from vendor.As soon as you get vendor confirmations through EDI system coverts to into inbound delivery.
If you are looking inbound delivery then you can use vendor confirmations.
Edited by: Sridhar Jayavarapu on Feb 24, 2011 5:32 PM

Vendor confirmation via EDI treated differently by MRP than Manually enterd

I have a strange situation with MRP.
I have a schedule agreement with the following information.
Date          Delivery sch            vendor confirmation
05/03/07          100                         100
05/10/07          100                         100
05/17/07          100                         100
05/24/07          100                         100
05/31/07          100                         100
06/07/07          100                         100
06/14/07          100                         100
Then I increase my independent requirments on 05/10/07 to 200.
If I have input my vendor confirmation manually via ME38, then MRP will add an additional Schedule line on 05/10/07 as I expected.   However if the vendor confirmations were sent in via idocs/edi then the schedule line is not added until the end of the confirmations.
Does anyone know why MRP would treat these differently based on if the confirmation were manual versus EDI?

It should not be treated saperately by MRP if it is posted manually or via EDI
i can think one thing that
do you have diff confirmaiton category for EDI and diff for manually than it can happen
so just make sure that all the confirmation category which you use is check for MRP relevant or not in
SPRO_MM_Purchasing-conformation-Set Up Confirmation Control-select your EDI confirmation contro key and click on confirmation sequence
and check here that the conf cat is check for MRP or not
if not than check than you will see that MEP will pickup that.

Vendor Confirmation via EDI

Hi
I am analising different possibilities to implement vendor confirmation via EDI?
Which Idoc - message type is suitable for Shipping Notification from vednor?
Is Inbound delivery created after Shipp. Notif comes to ERP?
What might be scenarios related to Purchase Order Confirmations.
ERP part only is my interest.
Thanks for hints
Mariusz

You can use Idoc message type DESADV to get confirmations from vendor.As soon as you get vendor confirmations through EDI system coverts to into inbound delivery.
If you are looking inbound delivery then you can use vendor confirmations.
Edited by: Sridhar Jayavarapu on Feb 24, 2011 5:32 PM

Posting Subsequent Debit via EDI(MIRO)

Hello All,
Any idea how to post the subsequent debit or credit via EDI using transaction code MIRO. We were able to post invoice/credit memo through EDI but not subsequent debit/credit.
Advance thanks for the reply.
Thanks
MP

Hi
Posting of subsequent debit and subsequent credit is not possible using EDI for invoice verification.
When you transmit invoice information via EDI, you
Cannot create subsequent debits
Cannot settle planned delivery costs
Cannot post with varying purchase order units of measure
Cannot post invoices for blocked purchase order items
Please check the link
http://help.sap.com/saphelp_erp60/helpdata/en/44/f50abcea3b11d194dc0000e83dd751/frameset.htm
Thanks & Regards
Kishore

Is direct GL account entry possible via EDI invoic message type?

Is direct GL account entry possible via EDI invoic message type? Is there a field in Invoic Idoc that matches the direct GL entry field. Some vendors may have surcharge other than tax and unplanned delivery.

This functionality is not available as standard. However, from release 470, you can use customer exit EXIT_SAPLMRMH_015 for direct posting to the G/L account or material account.
Please have a look at attached note 427137.

QM Block not triggered via EDI orders

Hello All,
Please help me with this problem "QM block not triggered via EDI Orders".
Sales Orders will be created using IDOC. When the sales orders was displayed using VA02, goto >> items >> schedule lines, there's no QM status violated being displayed in the delivery block column.
Kindly help me what logic will I applied regarding this matter.
FM used was IDOC_INPUT_ORDERS.
I need your comments/suggestions ASAP.
Thanks in advance.
Carina

hai,
Just check this it may help tou.
Program Name : YX30_UPLOAD_QUALITY_INFO
Quality Info Record for I30 System *
Original Transport Number : I30K903055 *
SYS id: SYS_30_1502_03_41_Upload Quality Info Records *
TDS id: TD_30_1502_03_41_Upload Quality Info Records *
UT ID: UT_30_1502_03_41_Upload Quality Info Records *
======================================================================
Change History *
Date | Change No | Name | Description *
yyyy/mm/dd | AAAYYYYMMDD | xxxxxxxxxxxx | *
REPORT YX30_UPLOAD_QUALITY_INFO MESSAGE-ID yx30_conversions
no standard page heading line-size 255.
include yx30_upload_quality_info_top. "Include for Variable Declaration & Selection Screen
include yx30_upload_quality_info_data. "Include for File read & Authority Check
*& At Selection Screen Output *
AT SELECTION-SCREEN OUTPUT. "PBO
PERFORM fill_parameters.
*& Start Of Selection Event *
start-of-selection.
Perform Authority_check. "Subroutine for authority check
Perform prepare_file. "Subroutine for preparing file
perform file_read. "Subroutine for File read
perform update_qi01. "Subroutine for Uploading data
perform write_error_log1. "Subroutine for writing error log
*& Form write_error_log
text
--> p1 text
<-- p2 text
*& Include YX30_UPLOAD_QUALITY_INFO_TOP
Type Declaration
Types: Begin of type_qtyinf,
matnr type matnr, "Material No
lieferant type char10, "Vendor
werk type werks_d, "Plant
frei_dat type char10, "Frei_Dat
stsma type char8, "Stsma
anwso_01 type char1, "ANWSO(01)
anwso_02 type char1, "ANWSO(02)
anwso_03 type char1, "ANWSO(03)
end of type_qtyinf.
Internal Table Declaration
Data: itab_qtyinf type standard table of type_qtyinf. "Internal table for QTYINF.
Work Area Declaration
Data: wa_qtyinf type type_qtyinf. "Work Area for QTYINF.
Variable Declaration
Data: v_file_qtyinf type string, "Source File Name
v1 type string,
v2 type string,
v3 type string,
v_file_return type string,
v_lin TYPE n.
*Selection Screen Declaration
selection-screen *
SELECTION-SCREEN BEGIN OF BLOCK blk1
WITH FRAME TITLE text-s01.
PARAMETER:
p_sysid(3) TYPE c OBLIGATORY , "Source System
p_bukrs(4) TYPE c OBLIGATORY , "Source CompCode
p_samshr type char30 lower case obligatory default '/sap_upload/' , "Samba Share Drive
p_object TYPE CHAR10 OBLIGATORY default 'MAT' . "Migration Data Object
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN SKIP 3.
PARAMETER:
cb_pfill TYPE c AS CHECKBOX DEFAULT 'X' . "Prefill values?
SELECTION-SCREEN COMMENT /1(79) text-s1a.
SELECTION-SCREEN BEGIN OF BLOCK blk3
WITH FRAME TITLE text-s03.
PARAMETER:
pa_filn1(500) TYPE c LOWER CASE
VISIBLE LENGTH 50 , "Filename AppServer
pa_dlimt TYPE c DEFAULT ';' . "Field Delimter
SELECTION-SCREEN END OF BLOCK blk3.
include bdcrecx1. "Include for the subroutine
*& Include YX30_UPLOAD_QUALITY_INFO_DATA
*& Form file_read
Subroutine for reading the source file into internal table
--> p1 text
<-- p2 text
FORM file_read .
DATA:
single_line TYPE string .
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_qtyinf FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
DO.
READ DATASET v_file_qtyinf INTO single_line. "Reading the content of file into line
IF sy-subrc = 0.
IF sy-index > 1. "skip header-line
SPLIT "Split the content of line into work area
single_line
AT ';'
INTO
wa_qtyinf-matnr "Material No
wa_qtyinf-lieferant "Vendor
wa_qtyinf-werk "Plant
wa_qtyinf-frei_dat "Frei Date
wa_qtyinf-stsma "STSMA
wa_qtyinf-anwso_01 "ANWSO_01
wa_qtyinf-anwso_02 "ANWSO_02
wa_qtyinf-anwso_03. "ANWSO_03
APPEND wa_qtyinf TO itab_qtyinf. "Appending Work Area to internal table
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET v_file_qtyinf. "Closing the files
ELSE.
MESSAGE e015 .
ENDIF.
DESCRIBE TABLE itab_qtyinf LINES v_lin.
IF v_lin LT 0.
MESSAGE e016 .
ENDIF.
ENDFORM. " file_read
*& Form fill_parameters
Subroutine for getting the file name
FORM fill_parameters .
IF cb_pfill = 'X'.
Preparing QTYINF File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO pa_filn1.
ENDIF.
ENDFORM. " fill_parameters
*& Form Authority_check
Authority Check
--> p1 text
<-- p2 text
FORM authority_check .
Authority Check For the Migration
AUTHORITY-CHECK OBJECT 'YX30_MIGR'
ID 'SYSTEM' FIELD p_sysid
ID 'BUKRS' FIELD p_bukrs
ID 'YX30_DMOBJ' FIELD p_object
ID 'ACTVT' FIELD '16'.
IF sy-subrc <> 0.
MESSAGE e010 WITH p_sysid p_bukrs p_object.
ENDIF.
ENDFORM. " Authority_check
*& Form prepare_file
text
--> p1 text
<-- p2 text
FORM prepare_file .
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO v_file_qtyinf.
CLEAR v3.
CLEAR v2.
Prepare Return File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_RETRUN_LOG_' p_bukrs '.CSV' INTO v2.
CONCATENATE '/sap_upload/' v3 '/' 'MAT' '/' v2 INTO v_file_return.
ENDFORM. " prepare_file
*& Form update_qi01
text
FORM update_qi01.
PERFORM open_group. "Opening a session
CLEAR wa_qtyinf.
LOOP AT itab_qtyinf INTO wa_qtyinf.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0100'. "Subroutine for mapping data
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'QINF-MATNR'
wa_qtyinf-matnr. "Mapping the material
PERFORM bdc_field USING 'QINF-LIEFERANT'
wa_qtyinf-lieferant. "Mapping the vendor
PERFORM bdc_field USING 'QINF-WERK'
wa_qtyinf-werk. "Mapping the plant
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=STAN'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-STSMA'.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma. "Mapping the status
PERFORM bdc_dynpro USING 'SAPLBSVA' '0201'.
PERFORM bdc_field USING 'BDC_CURSOR'
'J_STMAINT-ANWSO(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
IF wa_qtyinf-anwso_01 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01. "Mapping the anwso(01)
ELSEIF wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02. "Mapping the anwso(02)
ELSEIF wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03. "Mapping the anwso(03)
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ENDIF.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-FREI_DAT'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=QMBU'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma.
PERFORM bdc_transaction USING 'QI01'.
ENDLOOP.
PERFORM close_group. "Closing the session
ENDFORM. "update_qi01
*& Form write_error_log
text
--> p1 text
<-- p2 text
FORM write_error_log1 .
DATA:
single_line TYPE string,
v_msg TYPE string,
v_msg1 TYPE string.
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_return FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
CONCATENATE text-020 v_lin INTO v_msg SEPARATED BY space.
CONCATENATE text-021 v_lin INTO v_msg1 SEPARATED BY space.
TRANSFER: v_msg TO v_file_return.
TRANSFER: v_msg1 TO v_file_return.
WRITE:/ v_msg.
WRITE:/ v_msg1.
ENDIF.
ENDFORM. " write_error_log
with regards.
sowjanya.b.

STO Via SD or STO via MM

Hi Gurus,
I need to know the pros & cons of Stock trans. order via SD process & STO via MM.
Client need to know the exact diff & which business process is more advantageous.
Thanks
Jai

1)If you are working with the stock transfer procedure with LE outbound delivery (SD route), this has the advantage that the shipping activities can be processed with the R/3 System (picking, packing, printing the delivery note, and so on).
2)This has advantage of control function since dispatch department can control the material shipping out of the company.
Material should have sales view and this material should be maintained in both the plants
Thus the STO via shipping is studied and documented in very simple language
Difference between STO of MM and SD route is explained and same can be considered while configuring STO for client
Hope this helps
If you need more information pls info. Mail
Amit

Price conditions on Sales Orders via EDI

Hi,
I need to know if there is a way to bring prices over on the IDOC while posting a sales order via EDI. I have a situation where the price does not have to be determined based on condition records setup within SAP but rather update the price sent on the IDOC itself.
Thanks
MR

Hi,
Let the inbound Idoc have the price field and the price of the material. And keep the price condition type open/manual entry allowed. Once this is done the system will not do it from the condition record and will populate the data that is there in the Idoc.
Hope this helps.
Kind Regards
Chakradhar

Difference B/W creation of STO via ME21N and ME27

Dear all,
The requirement is to create a STO via transaction ME21N.
I am doing so using BDC Recording. But I believe that BDCs can not be used for creation of Application Documnets using Enjoy transactions.
For the same reason I tried to create the STO via ME27 but there wre certain fields
which I require to populate are not available in this transaction.
Can u please let me know what is the difference between the above transactions ?
Kindly help.

Hi karthick,
This 'F' has no meaning like 'N'.
But i think.. these are stands to denote application area.
F- for pruchase order
A- for RFQ
etc....
ME91F - Purchase Orders: Urging/Reminders
ME91A - Urge Submission of Quotations
ME91 - Purchasing Docs.: Urging/Reminding
ME91E - Sch. Agmt. Schedules: Urging/Remind.
See these all are for different purpose.
Regards
Sreekanth

STO (via EDI) extend delivery

Similar Messages

Maybe you are looking for