BAPI or IDOC for Advance Shipment in CS

Hello
I have to create Interface (inbound to SAP) for following function.
(1) Create Service Notification and Create Sales Order from Notification and need copy from contract.
     This function can execute by manual.
      1) IW51 create Notification and click ADV Shipment icon
       2) Input SO type for Subsequent SO of Contract and enter
       3) in SO screen, item adding by reference contract and enter
       4) Copy contract item and update Qty
        5) Back to Notiication and save. (automatically SO saved)
     But I can't find BAPI/IDOC for this procedure.
     If someone know solution, please let me know.
(2) Create Service Order and Create Sales order from CS order for Advance Shipment
   This function can execute by manual.
    1) IW31 create CS order and input component tab
    2) select component line and click ADV Shipment icon
    3) Input SO type for ADV SHIP and enter
    4) in SO screen, automatically component tab data copied and check this and back to CS order
    5) Save CS order (automatically SO saved)(CS order component changed to not relevant for reservation and ADV ship flag set to reservation)
   But I can't find BAPI/IDOC for this proceure.
   If someone know solution, please let me know
If some portion can use by BAPI/IDOC etc, it good for me.
Specially Link with Notification / CS order and SO is possible very useful for us.
Regards

check - VIEWPROC_V_TQ051
Regards,
Sonal

Similar Messages

BAPI or IDOC for transaction F-32

Hello everybody,
is there any bapi or IDOC for transaction F-32?
thanks,
Alejandro

Hi,
I'm not sure but I think the following's one can do the job :
BAPI_ACC_PYMNTBLK_UPDATE_POST
or
BAPI_ACC_BILLING_POST
I suggest you to take a look at the help,
Regards
Erwan.

Bapis and IDOC for Service order... etc.

Hi Experts,
Can any body please tell me what are the bapis for creating
following things.
Create Service Order or Sales Order
Update Service Order
Goods Issue & Goods Receipt
Inventory Balanceses
Purchase Requisition Information
Purchase Order Information
For this above are there any standard inbound and outbound
idoc for data transfer.
Thanks & Regards,
Chetan

Hi,
Thank you very much For the Information.
I had asked one more question below that.
"For this above are there any standard inbound and outbound
idoc for data transfer".
Thanks & Regards,
Chetan

BAPI or IDOCs for Quality info records

I want to know which BAPI or IDOCs is used to upload the Quality info records data from legacy system to SAP.

Hi Raghu
Below is the BDC program I was used for the same.
Program Name : YX30_UPLOAD_QUALITY_INFO
Author : Rameshwar Yadav *
Date : 2006-11-27 *
Description : The purpose of this program is to upload the *
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
Regards,
Sree

Bapi or idoc for electronic bank statement

may you please assist me on which bapi and or idocto use for elctronic bank statement idocand guide me on how to implement the two

Hello,
If you want to use Idoc for electronic bank statement then idoc type should be :FINSTA01 & message type is FINSTA.
For additional information check the following link: http://help.sap.com/saphelp_nw04/helpdata/en/e4/52ec78bfff11d295f400a0c9426c73/content.htm.
Hope this is what you were looking for .
Thanks.

Edi for advance shipment notification

the scenario is :.
Vendor will directly deliver goods to Customer XYZ and he will send ASN
(Advance shipment notification) through EDI to ABC company. can anyone please explain me the detailed step to create advance shipment notification through edi with all the transaction which need to be used and inbound delivery details.
thank you..

Hi,
Do refer the below Help Link it may help you...
Creation/Receipt of Advanced Shipping Notifications and Inbound - Third-Party Order Processing (TPOP) - SAP Library

Bapi or idoc for transfering activity list

hi,
Is there any BAPI or IDOC to transfer my task list to NON sap system i.e.MES ?
Thanks & Regards
MZI

Sorry
It should have /ISDFPS/TL01been (as tejasg suggests)
I inadvertantly put in a lower level
PeteA

Distinguishing between IDocs for Delivery, Shipment and Invoice

Hi Experts,
I have a requirement where I am triggering IDocs from SAP for Delivery Document, Shipment and Invoice and sending them to a third-party middleware everytime they are created in SAP, by configuring output types for these documents.
I want to know if we have any field in these IDocs's Structures that can be used to distinguish between the different documents such that we can identify which document has been received based on this field (or combination of fields)?
I tried to use Document Category for this purpose, but this field is not available in Invoice and moreover, the IDoc Segment names are different for every IDoc's message type.
The key point here is that I am not allowed to do any sort of Customization in SAP to achieve this and I can only go about using the Standard Functions inherently available in SAP.
Please suggest a possible solution for this predicament of mine.
Thanks in advance.
Regards,
Keerthi

Hello Keerthi
I do not see where the problem lies.
We exchange via FTP share similar documents with one of our logistics partner:
Inbound delivery (VL33N) => sent as DESADV.DELVRY03 => converted on SAP-XI to TRADACOMS ORDHDR => file suffix .LTI
Shipping Order (VL03N) => sent as SHPORD.DELVRY03 => converted on SAP-XI to TRADACOMS ORDHDR => file suffix .LTO
I am not a fan of functional file names yet if the third-party tools is not capable to distinguish between the documents based on their contents at runtime then we need old-fashioned unique file suffixes.
Of course the two ORDHDR messages can be distinguished based on their contents. The message contains a TYP segment with the following qualifiers:
TYP/TYP2 = '0430' = (shipping) order (= outbound delivery)
TYP/TYP2 = '0660' = inbound delivery
From this logistics partner we receive two different kinds of DLCHDR (delivery confirmation) messages:
TYP/TYP2 = '0670' = Proof of Delivery for (shipping) order => mapped to STPPOD.DELVRY03
TYP/TYP2 = '0695' = Goods receipt for inbound delivery => mapped to WHSCON.DELVRY03
The files have different suffixes yet they are not evaluated. SAP-XI just picks both messages and evaluates at runtime whether it has to transform the DLCHDR into a STPPOD or WHSCON IDoc.
Regards
Uwe

Standard BAPI or IDOC for QM data in SD

Hi all
I am using LSMW for uploading Quality Mannagement Data in SD (t-code QV51). If any Standard BAPI, IDOC or Funtion Module available for it then please sahre.
Aboli

check - VIEWPROC_V_TQ051
Regards,
Sonal

Designing EDI Interfaces for Advance Shipment Notification and POD

Our client does not engage in manufacturing and distribution of its products and components. They have developed partnerships with companies who provide distribution, manufacturing, shipping and movement services. They have authorized Forwarding Agents to transport the shipment. However, our client monitors and controls the business operations and remains the final authority in decision making.
The distribution company does the actual delivery and sends our client shipment confirmation (EDI-856). A single IDOC (SHPCON) comes in and performs the following functions
   Update the delivery document (set picking value based on what shipped)
   Generate a shipment document (with Handling Unit Information)
    Post Goods Issue
We are facing performance issue with this kind of setup and the remedy suggested is to have multiple IDOC types to come in and create the shipment document and do the PGI separately.
I would like to hear experiences from practitioners on how they designed this requirement with other clients

Hi Prabhahar,
Try in this transaction NACE.
Select V2 for Shipping. And click output types.
Select LALE (Shipping Notification to Sold-to-party) or LAVA (Outgoing Shipping Notification) and use the Program RSNASTED for EDI processing and customize with the help of ABAPer.
Hope this helps.
Thanks
Augustine Ponraj

Business Object (BAPI/IDOC) for production Order

Hi All
I have requirement where data is coming from legacy system to R/3 via XI to generate a production order. I am not able to get right BAPI/ IDOC for inbound Production Order. Can anyone has done similar scenario. Can u suggest me BAPI or IDOC for same. I am using IS-Mills 4.7 version for R/3
Thanx in advance
Regards
Vinod

HI Vinod,
I think U can use IDOC <b>LOIPRO01</b> for Production Order...
Regards,
Sridhar Reddy

GTS BAPI or BDC FOR Tcode /SAPSLL/PRODUCT_02

Hello All,
I need a help to upload data's in T-code /SAPSLL/PRODUCT_02 (SAP GTS ) Custom Product maintenance, i can't do with BDC because this t-code is having GUI, So kindly guide me how we can upload the data's in this t-code, and there is no BAPI or IDOC for this t-code.
Thanks in advance.

hi
try using this FM /sapsll/product_change
cheers
s.janagar

Handling unit creation in existing shipment via BAPI or IDOC

Dear all,
Dose any one tried and succeed packing deliveries items in an existing shipment in the shipment level via BAPI or IDOC.
I tried to use IDOC massage type SHPADV. The problem was that it's creates a new shipment with the same deliveries and pack their items, although I entered the existing shipment number.
With regards to "BAPI_SHIPMENT_CHANGE", it is seems like this BAPI is not an option. It is update the shipment in any shipment field but not creating HU in shipment level.
Dose there any solution via those options or there is any other solution.
Thanks in advance,
Itai

I tried simulating this LSMW (message type- PREQCR1, Baisc type -PREQCR101) and it is working fine. I used creation indicator = R in item segment - E1BPMEREQITEM and have not updated value for this field in Header. So try without any value for CREATE_IND in HEADER and just pass R in item.
yogesh

General questions on IDOCs and IDOCs for 2 Accounting Interface BAPIs

This post involves several questions pertaining to the topic of IDOC creation. I downloaded a couple of PDFs and tried googling for material on that, but things are far from being clear in my mind.
I tried to put my questions in some order, so we can follow a line of reasoning. Here we go, then:
I have one code where I there are calls to 2 BAPIs:
- BAPI_ACC_ACT_POSTINGS_REVERSE and
- BAPI_ACC_GL_POSTING_REV_POST
I am supposed to prepare/create an IDOC to perform the activities these BAPIs are responsible for, for the sole purpose of providing us much more details on the activities being executed in the system - this is one of the IDOC's features, if I got it right, its highly detailed logging of everything that is going on behind.
Now, the 1st question arises:
From the material I read, I understood that IDOCs are nothing more than data containers, whose sole purpose is to provide a means of communication between two different systems/parties - one of them would usually be SAP. If this is right, than what sort of IDOC would be this one I am supposed to build - if there's not going to be any inter-system communication ? Doesn't it sound strange that pure "data containers" can work as "logging functions" ? Please share some light here.
The 2nd question - after I understand what an IDOC really is - is
then connected to the job I have to do. I found 2 IDOCs which I think have the proper/correspondent basic types for the 2 aforementioned BAPIs. They are, respectively:
- ACC_DOCUMENT_REVERSE01 and
- ACC_GL_POSTING_REVERSE01
Getting back to my understanding of IDOCs, I got that every IDOC is generally made of one control record, data record(s), and status record(s). 3rd question: Where do the segments fit in ? Are the segments definitions of the Data Records ? And why is it that some IDOC types have header segments only and others doesn't have one ? (header segments are not the same as control records, right ?)
Finally, what is the general process flow for creating/preparing an IDOC ? I looked over a couple of forum posts about this but some of them differ one from another in the order of the steps, some don't mention this or that step, so I am still confused.
4th and last question: what comes first ? The definition of a partner, the bonding of a message type with an IDOC basic type, definitions of the inbound/outbound interfaces ?
Any help here would be highly appreciated.
Thanks in advance,
Avraham

Hi Jaya,
Answer 1. Class is a template for creating objects. Object can also be called as instance.
Interfaces allow you to use different classes in a uniform way (polymorphism).
Answer 2. Normal abap is a procedural programming where as by using abap objects we can achieve object oriented programing.
Answer 6. Source code:
In below code i have created a interface and a class which is implementing the interface. I have declared a reference variable of type interface and created a object. Then i have called a method.
REPORT ZABAPOBJECTS_INTERF.
      INTERFACE I1
INTERFACE I1.
METHODS METH1.
ENDINTERFACE.                    "I1
      CLASS C1 DEFINITION
CLASS C1 DEFINITION.
PUBLIC SECTION.
    METHODS: METH2.
    INTERFACES: I1.
ENDCLASS.                    "C1 DEFINITION
      CLASS C1 IMPLEMENTATION
CLASS C1 IMPLEMENTATION.
METHOD I1~METH1.
    WRITE: / 'This is a method one'.
ENDMETHOD.                                                "I1~METH1
METHOD METH2.
    WRITE: / 'This is a method two'.
ENDMETHOD.                                                "METH2
ENDCLASS.                    "C1 IMPLEMENTATION
START-OF-SELECTION.
DATA : REF1 TYPE REF TO I1.
CREATE OBJECT REF1 TYPE C1.
CALL METHOD REF1->METH1.
Question 7: Yes we need to create a class but most probably we use the existing classes.
Regarding BAPi's go through the below links,
http://www.sapgenie.com/abap/bapi/example.htm
http://www.sapdevelopment.co.uk/bapirfc/bapirfchome.htm
Regards,
Azaz Ali.

BAPI or IDOC to create the Delivery in R/3 for the SaleOrder created in CRM

Dear All,
When ever I create a sales order and save the sales order in the crm system, an outbound delivery is created in the R/3 system.
I have added some new fields in the tables LIKP and LIPS.(related to delivery)
Now I have to populate data into these new fields with the CRM data.
So can any one tell me when I create a sales order in CRM, does the system uses any BAPI or IDOC to create the Delivery in R/3.
The BAPI name or Idoc information will be very useful.so that I can extend them
In crm the BDOC BUS_TRANSACTION_MESSAGE is used.
Thanks in advance.
Regards
Shafath

Hi All,
I found a solution to my problem.
The BAPI BAPI_DELIVERYPROCESSING_EXEC will be enhanced to add the new fields into the BAPI structure.
The BADI /SPE/BAPI_DLVEXEC_EX and the user exit EXIT_SAPLV50R_CREA_001 will be used to populate the data into the new fields created in the BAPI structure and the new fields added into the tables LIKP and LIPS.
Regards
Shafath

BAPI or IDOC for Advance Shipment in CS

Similar Messages

Maybe you are looking for