Inbound Idoc to create SD invoice thru VF01

Hello All,
I was looking for an Idoc that allow me to create an SD invoice (and automatically then an FI posting) based on an SD order (as VF01).
I found some consultants talking about INVOIC, others about ACC_BILLING.
But after somes tests, none of the above works as expected. (-may be I am using a worng process code...)
Is there an Inbound Idoc where I can mention the same data as I will do in VF01 to generate an SD Invoice ?
Thank you All

There is no inbound IDoc, to my knowledge, and it'd be a very unusual scenario that would require invoicing through an IDoc interface. As soon as all the preceding transactions have been completed, not sure what sense it would make to wait for some kind of interface to give OK for the invoice creation...
Anyways, there is an option to run billing through a background job, which could be scheduled at regular intervals or based on an event. It'd be a very short program to get a document # and to trigger an event for the job or just run SDBILLDL directly, whichever is preferable.

Similar Messages

URGENT - create FI invoice thru idoc IDOC_INPUT_INVOIC_FI

Hi all,
I got a problem while creating a FI invoice thru the IDOC IDOC_INPUT_INVOIC_FI .
In the created FI invoice i need to populate some fields in the profitability segment ( like customer number... ) .
My problem is I don't know where in the idoc i have to set the value .
Can somebody help me ?
Best regards.
Bertrand.

Hi,
You can enter partner information in segment E1EDKA1
of IDoc type INVOIC02.
Not sure how much of this you already know, but I figured it doesn't hurt to include the following example:
Run transaction WE60, enter your IDoc type, and execute (F8). This will give you a list of all the segments and the segment fields. Expand the segment E1EDKA1 and then expand the sement fields. The first field is PARVW (you will see on the screen that there are various allowed values listed for this field, e.g. 'AG' = Sold-to party). The next field is PARTN in which you can enter the partner number (e.g. the Sold-to number).
You can use the Find function (after expanding all the branches) to look for any other type of fields you need to populate. Once you find the "business name" of a certain field within the segment documentation tree list, you will be able to see which IDoc segment the field belongs to. This is the place in the IDoc that you will set the value.
If INVOIC02 is not the IDoc type you are using, this same search technique will work for any IDoc type.
I hope this helps you out.
Best Regards,
James Gaddis

Inbound IDOC error while processing Invoice

Hi All,
I received the following error while processing an Invoice on an inbound IDOC:
Field BSEG-MEINS - does not exist in the screen SAPMF05A 0300
Message no. 00349
Diagnosis
The specified field does not exist on the screen
Procedure
Check your batch input data
Any assistance will be greatly appreciated.
Thanks, Inno

Hi
Please check which G/L Accounts were involved and verify that the Field BSEG-MEINS was set to 'optional' in Transaction OB14. The correct Field Status Variant
for the Company Code can be viewed with Transaction OBY6 and the Field
Status Group for G/L Account can be found with Transaction FS00 under
the Create/bank/inter Tab. This should eliminate the Error 00 349.
Regards
Javier

Inbound IDOC not creating B007 relationship (HRP1001)

Hi,
I have an inbound IDOC containing object type S (Position) and object type C (Job), plus various relationships including A007 and B007 between the Job and the Position.
All of the relationships get created except the B007 i.e. the Position cannot link to the Job? This is happening for some jobs only....
We checked with all the possible testcases but could not find the clue....
Kindly let me know if anyone have answer ??
Thanks in Advance.

Glen,
Thanks for your Quick response.
Firstly I would like to tell you that the relationship is not created for only couple of Jobs which were existed in the system. But if I do same by creating new records(jobs) its flowing perfectly.
It's giving neither error message nor the Subsegment for this created Object.

Relating outbound idoc to inbound idoc to create a document

We have a requirement to relate the outbound idoc to inbound idoc , transfer the data and create a document.
Kindly let me know the tcode / configuration steps of how can we relate the idocs.
Thanks,
Nalini S.

Hi Juan,
Check the IDOC: WMATGRP01. Hope it will be helpful for you.
BR,
Lokeswari.

Inbound idoc to create outbound delivary with ref to sales order

Hi,
       I am getting and inbound idoc from the external party to create Inbound delivary with reference to sales order.
       But my inbound process code FM(IDOC_INPUT_DESADV1) checking PO no. and item which is NON SAP PO no. and item in idoc. So, it is giving error PO doesnot exist in the system .
       I want to create Inbound delivary with ref to SO not with reference to PO.
        Pls check techincal details which i am using for inbound process :
        Process code : DELS
        Inbound FM    : IDOC_INPUT_DESADV1
        Message type : DESADV
         Idoc : DELVRY05
        Kindly help me.
Regards,
Manoj

Hi,
For creating inbound Purchase Orders, you can use Idocs PORDCR1.PORDCR101 or PORDCR1.PORDCR102. I have used this and they are working perfectly for us.
Reg,
NJ

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Execution of inbound idocs to creat a SO

Hi All,
I am trying to create a SO using a IDOC which has 190 Line items, but when i see the SO after IDOC has created it, i am seeing only 150 line items, which leads to mismatch in IDOC line items to VA03 tc.
Now my client want's to delete the SO and relaunch the IDOC as there is a mismatch, but this is not posiible as the IDOC status is 62, which reads "IDoc passed to application".
Kindly suggest me what to do in this context.
Awaiting your reply.

Hi,
Delete that sales order in SAP, if you can(i.e if it is not PRD system)
and recreate it again properly.
Regards,
Anji

Inbound IDOC to create an STO

Hi,
I'm trying to create an STO through IDOC PORDCR05,01,02.... but everytime the IDOC is throwing error message 51 saying that "Partner Role cannot be processed by BAPI_PO_CREATE".The error details says that "Only two partner roles are defined for BAPI_PO_CREATE............IP and GS".I've maintained the partner roles in SPRO, but the error is still coming.
Can anyone help me in this regard? Or can anyone suggest any IDOC which calls the BAPI_PO_CREATE1 instead of BAPI_PO_CREATE.
Thanks and Regards,

I'm trying to create the STO through IDOC PORDCR05 which internally calls BAPI_PO_CREATE, but everytime the IDOC is throwing the error message "Please enter material number or account assignment category" inspite of entering material number. There is no Account assignment category I suppose, because I'm using DOCUMENT Type "ZDD" or "ZUB".
Is there any way to rectify the error or can you suppose which all the fields I would maintain to trigger the IDOC ?
Thanks a lot for your answer.
Thanks and Regards

User Exit for Inbound Idoc Processing of Customer Invoice

Hi all,
I have to extend a standard idoc 'WPUBON01' to include a segment with Header Text Ids to pass header text displayed in VF03.
Can you please share the exit name so as a call to function module save_text be made and the header text gets saved in the respective Header Text Ids.
Thanks in advance.
Radhika
Edited by: Radhika7 on Apr 21, 2011 9:55 AM

Hi Radhika,
Not sure of the actual business scenario of your requirement, anyways you can try the below customer exits, and if they dont work please provide more info on the scenario.
EXIT_SAPLWPUE_102              IDoc WPUBON01 Before Document is Posted
EXIT_SAPLWPUE_104              IDoc WPUBON01 Before Inbound Processing
EXIT_SAPLWPUE_109              IDoc WPUBON01 After Inbound Processing
EXIT_SAPLWPUE_110              IDoc WPUUMS01 Before Posting
My bet would be on EXIT*109 to be of any help.
Regards,
Chen

Payment Terms wrongly getting updated using Inbound Idoc

Hi All,
I have a inbound IDOC which creates new invoice evrery time it gets triggered. In the function module attached with that IDOC there is a logic written to fetch the payment terms from the vendor master LFB1. System should display that Payment terms in tcode MIR4 (Display Invoice) as per the logic written in the IDOC FM. But, It is displaying wrong payment terms.
Select single ZTERM
into v_zterm
from lfb1
where lifnr = p_lifnr.
I have checked while debugging my logic fetches the correct payment terms (20NM) but the same is not getting updated in MIR4 . wrong value (42 Net days ) geting updated. Please suggest what needs to be done to correct this.
Thanks,
VB

Vikas,
Your quesion can be bit more clear. What is that 42 days..?? To my guess based on your payment terms due date might be calculated and kept as 42 days. If you can tell us about 42 days then someone can help you.
Regards
Venkat

Inbound idoc failure(vendor invoice not posted)

Hi All,
we have two SAP systems. SAP A and SAP B.
SAP A is the vendor for SAP B system we have created a sales order/delivery/out bound invoice in SAP A system.The sales order has BOM material with main item and sub items. We have the same material master data and BOM master data in system A and system B since we are following split architecture.
The outbound invoice(with main and sub item) in system A has generated an outbound idoc and the idoc has gone to SAP
system B. There are the usual segments like E1EDP01 for main item and another E1EDp01 for the sub itmes in the outbound
idoc.The message type is INVOIC and basic type INVOIC02 with no extension.
In system B, the inbound idoc (coming from system A) has failed giving the error message "higher level items not allowed". The
segment E1EDP01 for sub item is highlighted in red ! basically the inbound idoc in sap system B is posting a vendor
invoice since the inbound idoc in B is calling the FM IDOC_INPUT_INVOIC_MRM... I think this is doing vendor invoice
verification.
I have checked in system A, all is ok and the outbound idoc is ok but the issue is in sap system B, the inbound idoc has failed
with message "higher level items not allowed". The segment E1EDP01 for sub item is highlighted in red in inbound idoc in
system B. The segments are the same for inbound idoc in B and outbound idoc in A.
Can someone pls tell what is wrong in system B.(config or data issue) as we are managing both systems.
regds

Hi,
I am not sure if we can send both main and sub items thorugh inbound invocie idoc to create vendor invoice.
you can try to post the idoc by removing main items from the IDoc in WE19.
one more thing you should aware is you are not allowed to to create two E1EDP01 segements for the same PO item(E1EDP02).
check this as well.
Regds,

How to create Inbound Idocs in a ABAP program? Any function Module?

Hello Experts,
My requirement is : I have sales order data which I extracted from third party system in my internal tables. In the same box I need to create inbound Idocs and then consequently create sales orders.
I have used the function module IDOC_INBOUND_WRITE_TO_DB to create inbound Idocs from Sales Orders data in internal tables. I have populated all the data records with correct PSGNUM and HLEVEL values. My plan is to create inbound idocs with this function module and send those to IDOC_INPUT_ORDERS function module which creates Sales Orders.
If a sales order in the internal table in ABAP program contains only one item, then I am getting correct idocs. But if more than one item exists for a sales order then the line item segments which got repeated in Idoc are having PSGNUM and HLEVEL values as zero when I checked in WE02. As a result the hierarchy from the second item segment is getting disturbed and getting the status 60.
I populated T_EDIDD with data records from IDOC_INBOUND_WRITE_TO_DB.
To the function module IDOC_INPUT_ORDERS, T_EDIDC and T_EDIDD are the input. I observed that in T_EDIDD also the PSGNUM and HLEVEL values are blank.
I am getting Status 60 with message 'EDI: Syntax error in IDoc (segment cannot be identified)' for idocs which have more than one item.
I need to extract sales data from third party and create inbound idocs and create sales orders in one ABAP program only. I need to display corresponding Idoc numbers for the corresponding third party sales order number in a listoutput.
Can anybody please provide inputs?
Regards.

Hi Anjali,
Thanks for the response.
I have passed the PSGNUM and HLEVEL values while populating the data records. Then I sent the data records and control record information to the function module IDOC_INBOUND_WRITE_TO_DB. Inside this function module there is code to clear the PSGNUM values and HLEVEL values.
for compatibility: clear administration data of data records
           perform data_records_wipe
                                  tables
                                      t_data_records.
FORM DATA_RECORDS_WIPE
                  TABLES
                      T_DATA_RECORDS_IN STRUCTURE EDIDD.
LOOP AT T_DATA_RECORDS_IN.
    CLEAR: T_DATA_RECORDS_IN-MANDT,
           T_DATA_RECORDS_IN-DOCNUM,
           T_DATA_RECORDS_IN-SEGNUM,
           T_DATA_RECORDS_IN-PSGNUM,
           T_DATA_RECORDS_IN-HLEVEL.
    modify t_data_records_in.
ENDLOOP.
ENDFORM.                               " DATA_RECORDS_WIPE
This is the code which is clearing all the PSGNUM and HLEVEL values. After coming out of this function module we are getting the error idocs created with disturbed hierarchy.
I need to create INBOUND Idocs with the data in ABAP program.
Please let me know if any inputs? Is there any function module existing to create Inbound Idocs inside an ABAP program?
Regards

Create shipment from inbound IDOC SHPMNT05 ?

Hello All,
I would like to create an individual shipment when i receive from a partner an inbound IDOC.
I'm using Message type SHPMNT, Basic Type SHPMNT05, Process Code: SHPM and testing in WE19 via FM IDOC_INPUT_SHPMNT.
How can I start the creation of the shipment with this inbound IDOC ?
Is it possible ? or is it necessary to develop in user-exit the code to create shipment with function module (which one ? BAPI_CREATE_SHIPMENT ?)?
Thanks a lot,
My

Hello Reddy
thanks for your answer.
is there particular customizing to be done ?
i exactly use function BORES_IDOC_INPUT_SHPMNT
The inbound idoc is generated but i have the following status message 51 "Application document not posted"
What does it mean ? a problem of data in the inbound IDOC to create the shipment ?
Thanks a lot
MY

Issue while trying to create Sales Order from Inbound Idoc ORDER05

Hi All,
I am trying to create a sales order through an Inbound idoc ORDERS05 created out of a Purchase order. The header pricing conditions from the Purchase orders gets populated in E1EDK05 segment and this needs to go to the Sales order header conditions while trying to create the Sales order.
But when the fields are getting incorrectly mapped to the Sales order. Issue being, the segment E1EDK05-BETRG contains the condition value. But this fields gets populated to the KOMV-KWERT (condition value) screen field on the Sales order header conditions. But this should have got mapped to field KOMV-KBETR (Rate). If I look at the Purchase order, E1EDK05-BETRG is the field getting fetched from field KOMV-KBETR on the Purchase order. So this should have correspondingly got mapped to KOMV-KBETR on the Sales order as well.
This looks like a standard behavior. But if any of you have encountered this issue before please let me know if any Correction instructions are available for the same. If this some issue in Pricing conditions configuration, do let me know.

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

Inbound Idoc to create SD invoice thru VF01

Similar Messages

Maybe you are looking for