Error in Inbound Customer IDOC (WE19)

Hi All
I am creating Inbound Customer IDOC
Message Type : DEBMAS
& FM : IDOC_INPUT_DEBITOR.
But getting error(51) : "No batch input data for screen SAPMF02D 0340".
According to previous threads, I have seen this screen for Mandatory fields but I didnt found any.
Could anyone tell me what mandatory fields to enter in DEBMAS or the Solution for this Error.
Regards.

Hi Nikhil I am getting this error which you got it before but this time I am getting it in LSMW when creating customer master screen."No batch input data for screen SAPMF02D 0340"
what am i supposed to check?
Can u plz send me ur mail ID.

Similar Messages

Inbound Custom IDoc Processing

Hi,
I've created an Inbound Custom IDoc, Created the ABAP function module to post it to the application, configured workflow and IDoc processing. All my setup appears fine as I can create IDocs from our AS400 subsystem and trigger a successful posting via the IDoc test tool.
Having got this working I now want to automate the posting.
At present I create the IDoc's on our Legacy AS400 System and FTP them onto the SAP Application Server which runs on a Windows 2003 platform.
How do I get SAP to process each of my waiting Idoc's?
Any examples appreciated....

Hi
For CUSTOM IDOC inbound processing
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Check out this sample Function Module on the inbound system
FUNCTION Z_IDOC_INPUT_EMPREP.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Database Tables
TABLES: ZAK_EMPLIST.
Include programs
INCLUDE MBDCONWF.
Data Declarations
*--- Employee Header -IDOC
DATA: FS_EMPHDR_DATA LIKE Z1R_SEG1.
*--- Employee Details -IDOC
DATA: FS_EMPDET_DATA LIKE Z1R_SEG2.
*--- Employee Header - application data
DATA: FS_APP_EMPHDR LIKE ZAK_EMPLIST.
*--- Employee Details - application data
DATA: FS_APP_EMPDET LIKE ZAK_EMPLIST.
Program Logic
*---Initialize Work Flow Result
WORKFLOW_RESULT = C_WF_RESULT_OK.
LOOP AT IDOC_CONTRL.
*--- Check whether the correct message was passed to us
IF IDOC_CONTRL-MESTYP NE 'ZR_MSG'.
      RAISE WRONG_FUNCTION_CALLED.
ENDIF.
*--- Clear application buffers before reading a new record
CLEAR   FS_APP_EMPDET.
CLEAR   FS_APP_EMPHDR.
REFRESH FS_APP_EMPDET.
REFRESH FS_APP_EMPDET.
*--- Process all records and pass them on to application buffers
    LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_CONTRL-DOCNUM.
      CASE IDOC_DATA-SEGNAM.
        WHEN 'Z1R_SEG1'.            " Employee Header
          FS_EMPHDR_DATA = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING FS_EMPHDR_DATA TO FS_APP_EMPHDR.
        WHEN 'Z1R_SEG2'.            " Employee Details
          FS_EMPDET_DATA = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING FS_EMPDET_DATA TO FS_APP_EMPDET.
      ENDCASE.
    ENDLOOP.
*--- If data is ok
SELECT * FROM ZAK_EMPLIST WHERE ENUMBER = FS_APP_EMPHDR.
    IF SY-SUBRC NE 0.
      INSERT INTO ZAK_EMPLIST VALUES FS_APP_EMPHDR.
      INSERT INTO ZAK_EMPLIST VALUES FS_APP_EMPDET.
    ELSE.
      UPDATE ZAK_EMPLIST FROM FS_APP_EMPHDR.
      UPDATE ZAK_EMPLIST FROM FS_APP_EMPDET.
    ENDIF.
ENDSELECT.
IF SY-SUBRC EQ 0.
*--- Populate Return variables for success
      RETURN_VARIABLES-WF_PARAM    = 'Processed_IDOCs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      RETURN_VARIABLES-WF_PARAM    = 'Appl_Objects'.
      RETURN_VARIABLES-DOC_NUMBER = FS_APP_EMPHDR-ENUMBER.
      APPEND RETURN_VARIABLES.
*--- Add Status Reocrds indicating success
      IDOC_STATUS-DOCNUM           = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS           = '53'.
      IDOC_STATUS-MSGTY            = 'I'.
      IDOC_STATUS-MSGID            = 'ZE'.
      IDOC_STATUS-MSGNO            = '006'.
      IDOC_STATUS-MSGV1            = FS_APP_EMPHDR-ENUMBER.
      APPEND IDOC_STATUS.
ELSE.
      WORKFLOW_RESULT              = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM    = 'Error IDOCs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
*--- Add status record indicating failure in updating
      IDOC_STATUS-DOCNUM           = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS           = '51'.
      IDOC_STATUS-MSGTY            = 'E'.
      IDOC_STATUS-MSGID            = 'ZE'.
      IDOC_STATUS-MSGNO            = '007'.
      IDOC_STATUS-MSGV1            = FS_APP_EMPHDR-ENUMBER.
      APPEND IDOC_STATUS.
    ENDIF.
ENDLOOP.
ENDFUNCTION.
Good Luck and reward me for the same
Thanks
Ashok

Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Error While Creating Custom IDOC Segment using WE31

Could anyone please help me resolve this issue.
I am getting following error when trying to create a custom IDOC segment type using WE31.
"Name range violation: Name Z1WOHDR not permitted in SAP system"
Segment type trying to create: Z1WOHDR
Regards
Venu

Try changing the name , But i am not getting any such error with the name you are using.
Just Try with some onther name

Inbound custom IDOC function module

I have created a custom idoc and attached a process code to it. The proceesing function module, reads values from the idoc and inserts into a database table.
My question is will this function module be invoked simultaneously? If so, should I first lock the table before inserting and then unlock it?
Thanks in advance.

Hi,
As soon as the idoc reaches SAP, it will trigger the function module you have connected through process code.
If the table is used only by your function module no need to lock the same.
It is always good to lock the table before updating the same.
Regards,
Baburaj

Code Inspector / Extended Check - Error in Inbound Custom Function Module

I have created a new cutom FM for Inbound IDOC Application Posting.
In the TABLE   Parameter of FM the following Tables difined.
IDOC_CONTRL                     LIKE     EDIDC
IDOC_DATA                     LIKE     EDIDD
IDOC_STATUS                     LIKE     BDIDOCSTAT
RETURN_VARIABLES     LIKE     BDWFRETVAR
SERIALIZATION_INFO     LIKE     BDI_SER
while checking with Code Inspector Tool I got an Error for BDI_SER.( Last Table Parameter of the FM)
Syntax check warning
"BDI_SER" can be enhanced. After a structure enhancement, the semantics of the
parameter transfer may change.
Internal Message Code: MESSAGE G_B
(The message can be hidden with "#EC ENHOK)
Type "BDI_SER" or the type of one of its subcomponents can be enhanced. The semantics of the parameter transfer may change after a structure enhancement.
For the execution of a Remote Function Call (RFC), the actual parameter and formal parameter do not have to be of the same type. In the case of structure types, the actual parameter and formal parameter can contain additional components at the end. These additional components are set to their initial values.
Check whether the enhancement category of the relevant type correct is set or whether the category "cannot be enhanced" should be used.
How to fix this error? other wise how to supress the Message by adding "#EC ENHOK
where I have to add the Comment "#EC ENHOK.
please help to give details .
Thanks in advance.
Shar

In the source code you will have this in comment right, use the "#EC ENHOK.

Processing Customer IDoc

I am processing inbound customer Idoc. When I am testing from we19 with some values in E1KNB1M and E1KNKKM , it is processed successfully. If the initial Idoc doesn't have those segments I am populating it in the program with the same value and that time
Idoc processing fails.
Status Message ::: In company code M100 , lockbox 12 does not exist
/ Risk category 1 control area 6000 has not been created
comes.
Anyone face such types of problem?
Regards,
Tanmay

Take the Error IDoc, without changing anything, process again thru WE19, on debug mode.
Here you can find where is the problem, May this will help you.
aRs

ERROR IN INBOUND IDOC

Hi Expert ,
while i am prcoess a custom idoc ,
i am getting the following error
status no :53
Error Msg : Application document not Posted ,
( No status record was passed to ALE by the application )
data is comingin the receiving end ,pls help to solve the problem
points will be given to the solutions
thanks and regards
Renjith MP

Hi ...
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...
try & let us know ....
Reward Points if it is Useful.
Thanks,
Manjunath MS

'Purchasing document does not exist' error while testing Inbound PO Idoc

Hi experts,
i am working on Inbound PO Idoc scenario. I am testing Idoc in WE19 with ORDRSP mesage type.
Idoc type:ORDERS05
Process code:ORDR
FM:IDOC_INPUT_ORDRSP
while trying to create PO it is giving an error 'Purchasing document does not exist' in we05.
please suggest me how to resolve this???
Regards,
Bhuvan.

Hi,
first time i am testing this IDoc and i don't find any field in Idoc structure to provide purchase order value.
any more inputs plz??
regards,
bhuvan.

INBOUND program For custom IDOC

Hi ,
i have a one senario on creation of IDOC,that is interface for the transmission of the Acknowledgement of check Remittance and Supplemental interface,once the message is received Successfully through OUTBOUND program it triges the Acknowledge other wise it send one mail to respective team for that i need to create a one inbound program please explain me i am new in the area of ALE/ IDOC please give in deatials.
Thanks,
Harinath

Hi Harinath,
In your case SAP is sending <b>Check Remittance and Supplemental</b> data to legacy system which in turn need to send acknowledgement for that. And its going to be in form of an idoc. for this we dont have an idoc you need to create one from scratch. please find the steps to be followed to create a custom idoc.
1) Create Z segment with required fields(fields coming towards you) using WE31
2) Create Z idoc using segment created in step 1 using WE30.
3) Create Z message type using WE81.
4) Link idoc created in step 2 with message type created in step 3 in WE82.
5) Create Z function module to post the idoc in SE37. Include all validations, updations to tables, Error handling in source code tab of this FM.
6) Maintain Inbound process code using the FM in WE42
Coming to sending a mail, It can only be done using workflow. But i think in your case it is not required. so it need to be done manually.
Get back if you have any doubts.
Regards,
Younus
<b>Reward Helpful Answers!!!</b>

When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code".

Hi Experts,
When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code". As checked, we have configured OBCD and OBCA for the vendor and we are passing the Tax Jurisdiction code in E1EDP04 SAL segment. Can anybody give us some idea to resolve this issue.
Regards,
Sameek

Hi Sameek,
Please refer the below link. Hope it helps.
http://scn.sap.com/thread/1435286
Regards,
Chandan.

Error with Custom Idoc

Hi All,
I have created a custom idoc for creation of master data in the system. This custom idoc is using a custom function module to process the idocs. In the FM i have used Call transaction method to upload the master data in the sap system. Everything seems to be working fine.
But the problem is that whenever any external system creates more than one idoc, first idoc is posted successfully while others fail with an error message "No status record was passed to ALE by the application.". Please let us know how we can resolve it.
Correct Answers will be rewarded.
Regards,
Sridhar.

Hello
Refer to following thread:
The specified item was not found.
Thanks
Amol Lohade

Error in Inbound IDoc processing

Hi all,
While processing Inbound delivery IDocs(Status 64), we are getting an error "Cannot convert Dimensionless Units".
Please help.
Regards,
SP.

Hi Vijay,
The IDoc is a Delivery IDoc. The OSS Note that you have sent is for a similar error but is related to APO systems and hence I don't think it is related.
Has anyone encountered this error before...?
It says 'Conversion of dimensionless units is not possible'....
Regards,
SP.

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

Inbound function module for custom IDOC

HI,
I have created custom IDOC.I need to create inbound function module for that custom IDOC.Can any one send me sample
function module for custom IDOC.(what are all the import Export,tables parameters and exceptions that I need to create for function module)
Thanks&Regards
Rama.Mekala

HI Rama,
I presumed that You are talking about a FM to create inbound IDOC. So for creating inbound IDOC you can use '
    CALL FUNCTION 'IDOC_INBOUND_ASYNCHRONOUS'
    TABLES
      idoc_control_rec_40 = gt_edidc
      idoc_data_rec_40    = gt_edidd.
IF sy-subrc NE 0.
*    MESSAGE e000 WITH text-003.
* ELSE.
*    MESSAGE i000 WITH text-004 .
ENDIF.
just prepare edidc and edidd record in and pass it to the FM..
Hope this will work for you...
Thanks

Error in Inbound Customer IDOC (WE19)

Similar Messages

Maybe you are looking for