Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

Hello,
the above segment is missing in the inbound idoc - basic type pexr2002.
I have checked in TC-we30 and its available there.
but still the idoc is getting generated without this segment.
can someone suggest.
thanks
Arun

Hi All,
I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002 and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
We have done the following steps:
- BTE 2441 is available on our release
- house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
- entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
- code maintained in ZXF08U04
The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
Can you advise what we might be missing please?
Thanks and regards
Mike

Similar Messages

How to write processing code for the Inbound IDOC to the R/3 ??

i m having a file -> XI-->R/3 scenario,
IDOC is being sent from XI to R/3,
can u guide to me to write a processing code for the Inbound IDOC to the R/3,
since i m new to ABAP and ALE technology, can we provide me any blog for doing that.......or guide me....

Hi Sudeep
Simple File to Idoc scenarion blog
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
Also see the blog
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar.
Configuration of IDOC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
Regards
Santhosh
*Reward points if useful*

Segment E1EDP36 not active in the DELFOR02 IDOC type.

Hi All,
I have been working with creating extensions for Idoc type DELFOR02 inn ECC 6.0. But for the basic idoc type DELFOR02 , the segment E1EDP36 is not active here.i.e., the idoc generated does not carry data for this particular segement.
This segment depends on entries in a structure xisautoeklwes ( include LEINMF3S, line 130). The underlying table for this structure would be ISAUTOEKLWES(Last Deliveries for FLAB).
Could anyone throw light on how this structure will be filled or how it has to be filled if I can make changes to the customer exit available there.
Thanks,
Savitha Patil

Hi Gearge,
To add custom segments, you should create an extension.
the TCODE is we30.
Refer this link:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

Some Data Missing in the inbound Idoc received from Gentran

Hi,
We are receing one custom message type with the basic type ORDER05 in SAP from Gentran. When we checked the destination file generated in Gentran, its showing data for all the segments. However in SAP when we checked the corresponding idoc we find the segment E1EDP05 is missing. The Gentran team says they are placing the destination file in the unix server of SAP. However we dont find these files in the SAP Unix server. Could anybody advise what could be the problem and where we need to check further ?

Gentran will never be able to create an IDOC within SAP. Here is what happens:
> Gentran creates a flatfile/XML which is in the IDOC format (the one which you can see in WE60).
> Gentran then places this flat file/XML in a folder on Application server. This can be UNIX, Windows NT, etc..
> Gentran then triggers the Startrfc.exe which will trigger EDI_DATA_INCOMING function module.
> This FM will parse the data, check it for consistency of the defined standards, then write the control record into EDIDC and corresponding data records into EDID4 and updates the relevant statuses (i.e. 01 - added, etc). It'll then look into the partner profile setup, look for process code and moves the status to 64 and calls the inbound FM which will post the application document.
In you case, you need to find out what file is coming in and where E1EDP05 has missed. The data will only be sent by Gentran. The inbound function modules will never update IDOC data records (unless there is a customization). The status records are updated.
If E1EDP05 is not mapped and sent by Gentran and you still used to see it, then there should have been a customization in place to add values to IDOC segment fields. Try to get the final file that is mapped from either X12/EDIFACT and then see if E1EDP05 segment is present in there. If it is present then upload the same file into AL11 using CG3Z and call EDI_DATA_INCOMING or WE19 to process it. Once processed, you'll can observe if E1EDP05 is being created or not.

User Exit available for basic inbound idoc type MBGMCR01 in SAP R/3

HI,
We are looking for the User Exit for BsicIdoc MBGMCR01.
When we create confirmation in EBP, this idoc gets triggered from EBP to R/3 to create goods receipt material document.
Regards,
Nikhil.B

Hi
<b>Please go through the following links, for all the required details -> </b>
GRN IDOC Transfer to ERP - MBGMCR01 ( 2 IDOCS created)
Re: GR IDOC Number
Re: Confirmation screen field to be mapped to backend field
Re: Delete goods confirmation in SRM3.0
Re: Not able to change confirmation date
Confirmation against Backend PO for SRM@ERP2005
Re: SRM Confirmation # in R/3
Re: Goods Confirmation not transferred to backend!!
Hope this will definitely help.
Regards
- Atul

User exit / BADI for the MATQM01 IDOC type?

Hello,
I am working on a Material Master conversion that will need to include the Material Inspection Setup. Using BD10 to send the material 'In Full' generates these MATQM01 IDOCs successfully. As part of this conversion I need to map some old plants to new plants.
Is there a user exit or BADI within the MATQM process that I can use to accomplish this?
The BADI/Exits for BD10 do not access the MATQM data. There are no exits listed for QL11 which is the standalone code for creating MATQM idocs.
Any help would be appreciated!
John

Thank you guys for the replies. I will try the Rules and Filters approach to implement the logic I require. If the logic is too complex then I will go with the z-copy of QL11.
Thanks!

How to block the status mail for an inbound Idoc to a specific user

Hi,
I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
Thanks,
Santosh

Hi,
I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
Thanks,
Santosh

Inbound Idoc type for posting Non-PO Invoice

Hi,
I am looking for an inbound Idoc type to post Non-PO Invoice. The Idoc types INVOIC01 and INVOIC02 helps me to post the invoice with reference to PO. But I am looking for the Idoc type to post the invoices without reference to PO i.e., For example to post the transaction FB60 (Enter vendor invoice without ref to purchase order).
with regards,
suresh

Hello Deep,
I know it might be quite late for you for this answer, nevertheless I will write that, because there are lots of question like yours. bapi_incominginvoice_park is also a suitable bapi for you. All you need to do is call it this way:
data: headerdata like bapi_incinv_create_header value is initial,
        table_item type table of bapi_incinv_create_item,
        gl_account like bapi_incinv_create_gl_account,
        table_gl type table of bapi_incinv_create_gl_account.
* fill headerdata and table_gl, leaving table_item empty
CALL FUNCTION 'BAPI_INCOMINGINVOICE_PARK'
    EXPORTING
      HEADERDATA                = HEADERDATA
*   ADDRESSDATA               =
    IMPORTING
      INVOICEDOCNUMBER          = lv_docnr
      FISCALYEAR                = lv_year
    TABLES
      ITEMDATA                  = table_item
*      ACCOUNTINGDATA            = table_acc
      GLACCOUNTDATA             = table_gl
*   MATERIALDATA              =
*      TAXDATA                   = table_tax
*   WITHTAXDATA               =
*   VENDORITEMSPLITDATA       =
      RETURN                    = lt_return.
This works perfectly for me, creating a mir7 document without refering to a PO. The trick here is to fulfill the glaccountingdata importing table while leaving itemdata empty.

RCVPOR is missing the Inbound IDoc

Hi all,
I am getting IDoc from the XI with the status code 56.
I found that receipt port is missing in the control record.
If I use sender partner type as LS, it is working fine. When I use the sender partner type as KU IDocs are not getting posted successfully, the port for the recipient information in the control record of the inbound IDoc is empty and all other filled are filled.
Any suggestions please
Thank you
Regards
Harsha

Dear Harsha,
can you explain how you solved the issue - I am experiencing exactly the same problem. I am receiving the same Message type from several other systems (not LI, but LS), and we are receiving other message types for the same partner. -> in all other cases the RCVPOR is filled correctly.
We are using webMethods and not XI, the RCVPOR is sent correctly by the middleware.
brg Karl

How to get the inbound idoc for the newly created inbound Idoc FM

Hi,
I have created a new function module to process the Inbound idoc. I need to have a idoc to check my function module, whether it is working fine or not. How I can get the data. Do I need to have the idoc from the partner ? Please help me ASAP.
Thanks,
sreenivas.

Hi Sreenivas,
Go to WE19 and get any of the your present idoc with the idoc type
then go to BD20...execute the same idoc...and there you can create the IDoc, and process the same with the Inbound function module tab..( give the FM you are using as the process code.)
from there you can do the debugging aswell of that FM
Thanks

Find the Inbound IDOC

Hi Experts,
I have a requirement to get the Inbound IDOC for particular PO. I have used the following method:
http://forums.sdn.sap.com/thread.jspa?threadID=1082790
That means using tables:
A) SRRELROLES
B) IDOCREL
This is working for most of the cases except if the inbound IDOC is amended by the sender ( ex:- requested quantity changed ).
1. If inbound IDOC received without any changes, it will be there in SRRELROLES as roletype = 'INBELEG'.
2. If inbound IDOC received with changes it is not there in SRRELROLES.
Could you please help me to resolve this issue?
Thanks,
Chaminda

Hi,
Thanks for your help.
anyway, finally i had to use the time consuming way as there is no any other way.
1. Get all the ORDRSP Idocs from EDIDC based on the selected date range
select docnum status
      into table lt_edidc
      from edidc
     where credat in p_date1 and
           mestyp = 'ORDRSP'.
    if sy-subrc eq 0.
      sort lt_edidc.
2. Get all segment data records for the control records
      select mandt docnum counter segnum segnam psgnum hlevel dtint2 sdata
        from edid4
        into table lt_edid4
         for all entries in lt_edidc
       where docnum = lt_edidc-docnum and
             segnam = 'E1EDK02'.
3. to imporve the performance, i have used BINARY SEARCH when search back the IDOC from PO.
Thanks,
Chaminda
Edited by: chamindakrat on Feb 17, 2012 12:07 AM

Creating Delivery based on the Inbound IDOC received.

Hi all,
I have a requirement where in, Outbound Delivery for Sales order is to be created based on the inbound IDOC received from a third party. The standard idoc type DELIVERY03, requires the Delivery Number for updating the order but it cannot create a delivery number.
Can any one suggest which IDOC type can be used for this or if there is any alternative solution?

Hi,
You can use FM IDOC_INBOUND_WRITE_TO_DB to create an inbound IDoc.
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
    EXPORTING
      PI_STATUS_MESSAGE       = I_EDIDS
    IMPORTING
      PE_IDOC_NUMBER          = DOCNUM
      PE_STATE_OF_PROCESSING = STPROC
      PE_INBOUND_PROCESS_DATA = I_TEDE2
    TABLES
      T_DATA_RECORDS          = I_EDIDD
    CHANGING
      PC_CONTROL_RECORD       = I_EDIDC
    EXCEPTIONS
      IDOC_NOT_SAVED          = 1
      OTHERS                  = 2.
Check the following link:
http://www.sapbrain.com/TUTORIALS/TECHNICAL/IDOC_tutorial.html
<b>Reward points</b>
Regards

For the new delivery type created the Idoc is not getting triggered

Hi All,
I am facing the following problem:
For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
The Idoc being used is: DESADV01
Message type :DESADV
Thanks,
Geeta

I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

Workitem is not generating for an Inbound Idoc

Hi All,
The problem I am facing, when inbound idoc is processing in SAP, if there are any errors occurred, it would generate a work item and that will be sent to user Inbox (SBWP) as per the workflow. Here it is not generating a work item for an inbound idoc where is there is an error. So user is not receiving work item mail to inbox, to check about the idoc error. This idoc has been processed through the function module.
Could you please let us know your input on this issue.

Hi Hitu,
The problem could be at multiple places.
To debug check the workflow which sends the workitem to the user when an error occurs.
Check if this workflow is getting triggered when the error occurs. If yes, then check the step whre this workflow fails.
Else, check the event linkage of this workflow and check if the associated event is getting triggered or not. If yes, check if the event linakge is active for the workflow.
There could be other places as well to diagnose the error.
Check if these inputs gives you some direction.
Regards,
Saumya

Where to put break point when debugging the inbound IDOC processing

Hi, Dear Experts,
If IDOC has error and want to debug, which program or function module to put break point when debugging the inbound IDOC processing
Thank you so much!
Helen

It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

Similar Messages

Maybe you are looking for