Error in Idoc Invoic01 ?

Hi all,
I am using message type INVOIC and IDoc type INVOIC01 .
Inbound process code SD08 and Outbound process code INVL.
Out put type RD00 to create Logistics invoice verification when the billing document is created.
It is giving error as 'A company code cannot be determined for LS XX04'.
Where XX04 is the vendor.
Though i maintained the company code details in OBCA , it is still giving the error.
So please help me on solving this error ?
Thanks,
Vamshi.

Hi Vamshi,
The system cannot determine the relevant company code since the allocation of the data transferred in the invoice is missing in Financial Accounting customizing.
The company code can be determined outside of the system and be put into the intermediate document (for example, from the EDI subsystem). Then the company code must be put into the E1EDK14 segment and ORGID field and the value "011" used as the qualifier.
Some hints from OBCA,
1.
Your EDI partner is the vendor '4711'. In this case:
The partner number is '4711'.
The partner type is 'LI' (vendor).
Your ALE partner is an SAP system that is addressed by your system (using RFC) with the name 'ID3MDT800' (logical name). In this case:
The partner number is 'ID3MDT800'.
The partner types is 'LS' (logical system).
2. Company Code Name in the Invoice
The name of the company code in the invoice must correspond to the name for our company transferred by the EDI partner. EDI incoming processing needs this name to be able to uniquely determine the company code to be posted to.
Technical note:
The name is taken from the intermediate structure INV_ID01, segment EDI_Z3 (invoice recipient), field EDI_Z3-NAME1.
The name for the intermediate structure INVOIC01 is taken from the segment E1EDKA1 (qualifier 'RE'), field E1EDKA1-PARTN or E1EDKA1-NAME (if E1EDKA1-PARTN is empty).
3. Company Code
The company code is an organizational unit within financial accounting.
Hope it resolves your issue.
Thanks & Regards,
Nagaraj Kalbavi

Similar Messages

Idoc INVOIC01

Hi all
We are making creating parked invoices for PO's using idoc INVOIC01. The functionality should be the same as that of transaction MIR7. In MIR7 we can enter a document reference (required field). If an invoice is already created with the same reference, the transaction gives an error (M8-108).
In the idoc we have filled segment E1EDK02 as follows,
qualf = 009
belnr = reference number.
The reference number is filled correctly, but the invoice is posted anyway.
Is it possible to have the same checks during idoc processing and how should i fill the segments to achieve this??
Regards,
Bert

Thank Amit.
I tell you: I am designing an interface and I am using INVOIC01 idoc.
I need to fill the fields of the structures and I don't know What fileds I must to fill for I indicate
the invoice is a Park invoice.
I hope you understand, and help if you can.
Thanks .-

Which field from idoc INVOIC01 maps to Item Text field in MIRO transaction?

Hi
Will anybody please tell me which of the field in which segment of IDOC INVOIC01 maps to Item text (INVFO-SGTXT) field in Basic data tab of MIRO transaction

Thanks Ravi for your response.
But I have tried with all fielsd related to texts in IDOC but it is not being filled in transcation .
If you see the F4 help in text field then Text Id is four character and when I manually assign this in transactin then it is putting = symbol in fron of the id. And then if we save or go to other tab then it is filling text.
I am not able to find the error bcoz document is being posted through idoc but text field is not getting filled.

Error in Idoc with status 26

Hi,
IDOC showing an error messge when syntex check.
EDI: Syntax error in IDoc (segment cannot be identified)
Diagnosis:
The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
This error can have several reasons:
The segment E1EDP19 is assigned to a group whose header segment does not occur.
The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Please help me....
Regards,
Sudha

Hi,
I have pasted a portion of my code:
DATA: BEGIN OF GT_EDIDC OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC.
DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC1.
DATA: BEGIN OF GT_EDIDD OCCURS 0.
        INCLUDE STRUCTURE EDIDD.
DATA :END OF GT_EDIDD.
DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
        INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
DATA : END OF GT_Z1ZPSOBJLOC.
* Control Record
FORM BUILD_CONTROL_RECORD .
GT_EDIDC-MESTYP = C_MESTYP.
GT_EDIDC-IDOCTP = C_IDOCTP.
GT_EDIDC-DIRECT = C_1.
APPEND GT_EDIDC.
ENDFORM.                    " built_control_record
*&      Form built_data_record
* Data record
FORM BUILD_DATA_RECORD .
LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
    GT_EDIDD-MANDT = SY-MANDT.
    GT_EDIDD-SEGNAM = C_SEG.
    GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
    APPEND GT_EDIDD .
PERFORM DISTRIBUTE_DATA.
ENDLOOP.
ENDFORM.                    " built_data_record
*&      Form distribute_data
* Distribute Data
FORM DISTRIBUTE_DATA .
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = GT_EDIDC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
      MASTER_IDOC_DATA               = GT_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
CASE SY-SUBRC.
      WHEN 1.
      MESSAGE E004.
    WHEN 2.
      MESSAGE E005.
    WHEN 3.
      MESSAGE E006.
    WHEN 4.
      MESSAGE E007.
    WHEN 5.
      MESSAGE E008.
    WHEN OTHERS.
* Do Nothing
ENDCASE.
COMMIT WORK.
* Clear IDOC data internal table after use
CLEAR GT_EDIDD.
REFRESH GT_EDIDD.
ENDFORM.                    " distribute_data
Hope it proves useful.
Regards,
Gayathri

Document type for Subsequent Credit/Debit for idoc invoic01/02

Hi SAP Gurus,
We are implemeting an interface to post incoming invoice with idoc Invoic01 idoc type.
We could able to post debit invoice and credit memo using document type in idoc (BSART) as "INVO" and "CRME".
But we would also like to post Subsequent Credit/Debit memos also with this idoc type but not sure what should be used in document type field ( BSART) in idoc.
If any one has come across this scenario please suggest whether is it possible to use Invoic01 idoc type to post Subsequent Credit/Debit notes if yes what is the document types used? also I see in OBCE transaction we can only mention Invoice document type for debit and credit invoices only. How to handle this incase of subsequent Credit/Debit invoices.
Thanks.

Hello Rish,
Please, be aware that if you look at the document at MIR4/MIRO etc, they will apear as a INVOICE/CREDIT MEMO (in the "Drop down" box, in the top of transaction)even if they are sub. credit/deb, but that is the standard system behavior ! In order to check if it is a Subcequent debit/credit, you can check directly into rbkp table or even better, just check in the PO history! it will be in a separate category !
Give it a check if this is not the case!
Regards!

Error sending Idoc's to SAP

Hi,
I'm getting error in file-XI-SAP scenario. File is read and transformed to Idoc ok, but then I get this kind of error message in SXMB_MONI:
<SAP:Stack>Error: Basic type 'HRMD_A01' is unknown</SAP:Stack>
What I'm I missing in the scenario?

Hi Tapio,
Take a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Error: No IDocs could be sent to the SAP BW using RFC.
Hope it helps you.
Cheers,
Chandra

Getting Error in Idoc.

Hi all,
I m getting this error in idoc..
Entry in outbound table not found.
I doc number is generated..
also giving Program code ..check and tell me whr can i do change..
Following is program for idoc...
REPORT ZNA_IDOC .
*TABLES: CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
TABLES : ZNA_ID.
DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control
*Record
KUNNR TYPE ZNA_ID-KUNNR, " SEGMENT ORDER DATA
VBELN TYPE ZNA_ID-VBELN.
*QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
DATA : ZORDER LIKE ZNA_ID OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE. "Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated
"Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZNA_I'.
PARAMETERS : ZID LIKE EDIDC-MESTYP DEFAULT 'ZID', "Message Type
C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS', "Partner type of receiver
C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'D11CLNT100',
C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000009',
C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'A000000008',
C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'D11CLNT210',
C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZNA_IT',
C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'. "Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*& Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = ZID. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
APPEND S_CTRL_REC.
ENDFORM. " generate_control_record
*& Form send_idoc
FORM SEND_IDOC.
*SELECT * FROM ZNA_ID INTO TABLE ZORDER.
ZORDER-KUNNR = '1'.
ZORDER-VBELN = '101'.
**ZORDER-QUANTITY = QUANTITY.
APPEND ZORDER.
T_EDIDD-SEGNAM = C_ZRZSEG1.
T_EDIDD-SDATA = ZORDER.
APPEND T_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
MASTER_IDOC_CONTROL = S_CTRL_REC
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
MASTER_IDOC_DATA = T_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
IF SY-SUBRC = 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
COMMIT WORK.
LOOP AT T_COMM_IDOC.
WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
ENDLOOP.
ENDIF.
ENDFORM. " send_idoc
thx...

The program is probably correct, however, it seems that you haven't completed the 'customizing' just yet. The parameters entered in S_CTRL_REC contains entries which have not yet been maintained in the settings.
Have a look at the settings. I have no SAP system available right now, so I can't tell you what transaction is needed, but first have look at WE20 (use transaction menu WEDI).

Regarding Getting Error in Idoc .... Outbound table not found

Hello everyone
I am working on ALE/Idoc, at the last i am getting error that idoc has created but cannot be send, I am using XML port (not file) so giving Physical Dictionary, please solve my problem where i have to change. please reply its urgent.
Thanks & Regards
Vimarsh B.

Dear,
The addon is a third party addon which was developed by CitiXSys. so the support is provided by the partner who developed the addon.
Go to the vendor Citixys for further support will give you a quick reply.
Regards
Apple

Error in IDOC generation

Hi Gurus,
I have got an Error in IDOC Processing from other interface.
The IDOC status is 51 and we are using it to create Promotion Deal in
SAP ERP through IDOC from other interface.
The Error i am getting in Status Record is that "Promotion is Duplicated
along with Promotion Deal Number"
I have also checked the Promotion Deal No in VB 33 but it is not existing.
Please could you suggest where is the possible error.
I have also checked the Control Record it is correct.
Awaiting for response.
Thanks,
Sam.
+

Hi,
Reprocess the IDOC by using the T.Code "BD87".
Even if the same error persists,try to change the data manually by using the T.Code "WE19".
Check with the ABAPer for debugging the code.
Regards,
Krishna.

Syntax error in IDoc (too many repetitions of a segment)

Hi,
I tried to load master data from R/3 into BW system. The load is not ending and the IDoc error message is displaying,
The error message is " EDI: Syntax error in IDoc (too many repetitions of a segment) with status 26" .
I tried to analise the issue and checked in the Idoc List Outbox of BW system. I found Red status message with number 26 stating " Error during Syntax check of IDoc (Outbound) and the message type is RSRQST.
Could any one help me out in solving this problem. Reply to the message if any more information needed.
Thanks in Advance.
Regards
Koushik

I'm getting the same error. I think it is because I have a InfoPackage selection routine, that selects more than 1000 select conditions. I guess it is a parameter that needs to be changed somewhere. Any help on this one?
BR
Øyvind

Getting error in idoc FD 008

Hello ,
i am getting an error in idoc which is related with Tax code & Tax rate conversion in EDI . The Message number is FD 008 and message is "Assigning a new tax key for and VAT .000 not possible .
Can anyone please help me what could be possible cause of this error and how can i correct it.

hello,
see if your tax code has a correct value and it is not blank.
best regards,
swanand

IDOC INVOIC01 - fill in Personnel Numner MIRO

Hi guys
I want to fill in the field personnel number in the transaction MIRO (PO reference- data - DRSEG-PERNR) by posting an invoice with a LSMW based in the IDOc Type INVOIC01.
I am new to LSMW and IDOC any help will be welcome
Thanks in advance
J

Thanks fot the reply
But I can't use recording because it must go via the IDOC INVOIC01 with FM IDOC_INPUT_INVOIC_MRM -> I want to put the field DRSEG-pernr via this Function Module.
Anyone any idea??
Thanks in advance
J

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

Hi all,
I have extended the the standard IDOC MATMAS05 classification view with structure as below-
E1MARAM                        Master material general data (MARA)--->Mandatory segment
     Z1KLART                        KLART --->Extended chaild to E1MARAM
         Z1CLASS                        segment for class --->Extended chaild to Z1KLART
         Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
     E1MARA1                        Additional Fields for E1MARAM
     E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to
E1MARAM )
I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
Please help to resolve the issue.
Thank you.
Edited by: sanu debu on Apr 30, 2009 11:25 AM
Edited by: sanu debu on Apr 30, 2009 11:31 AM

Hi,
   You cannot add an segment in the middle of other segments.
YOu have to add any segment at the last.
If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
Regards,
Ravi Kanth Talagana

Error in Idoc Invoic01 ?

Similar Messages

Maybe you are looking for