Basic IDOC Receiver Issues - help

Hi,
I'm just starting development with the .Net connector and am trying to get the sample IDOC sender and IDOC receiver to work.
We have a remote test system with SAP, connected via a VPN from my site. A SAP Router is used for the GUI connection to SAP and I'm setting the sapDestination.SAPRouterString in the IDOC submit sample.
The IDOC sender is working and I can see the sent IDOCS in the SAP GUI, but I cannot get the IDOC receiver to work.
I have defined a TCP/IP RFC destination, with the IP address and program ID of my program, but the test button on the RFC destination does not work.
Also, after I start the IDOC receiver sample, transaction SMGW (Gateway Monitor) does not list my application.
Please could someone verify what I should configure on the SAP test system and what parameters I should be providing to the sample IDOC receiver program ?
Thanks,
Andrew

Managed to get the correct gateway/host combination and my application now registers !

Similar Messages

I am receiving Basic Idoc Type error while I am executing SWO1 for BKPF

Hi
I am receiving Basic Idoc type error message while I am trying to test BKPF object. Please note that the Business Object is delegated to a custom BO. Can anyone tell me where the linkage is established between IDOC type and BO.
Thanks
Arghadip

Arghadip,
Can you check the transaction WE57?
Thanks

Help to read the complete basic idoc structure

Hi,
I have the following Basic Idoc structure
1. /DSD/HH_CONTROL01- Control data for hand held interface.
1.1 /DSD/HH_E1CTHD01- Control data header.
1.1.1 /DSD/HH_E1CTAD02- Control idoc- Application data header
1.1.1.1 /DSD/HH_E1CTID03- Control idoc- Application data item
1.1.1.2 /E1WXX01- Segment for customer enhancement to be used as requirement.
OBSERVATION----
1. The basic idoc (1) is found in table EDBAS and description in EDBAST.
2. The segments (1.1.1.2) are in table EDISEGMENT and EDISEGT.
3. All the other structures (1.1), (1.1.1), (1.1.1.1) are found in tables EDISDEF and some in EDISEGMENT.
QUESTIONS----
1.What query can I write to get the above basic idoc structure?
2.How are the relationships mapped among the tables?
Thank you, points will be awarded for your time and answers.

REPORT ZPGM_BASIC_IDOC_IMPRT_TO_PCNTR.
TABLES: EDBAS, " Basic types
        IDOCSYN. " Syntax Description for Basic Types
DATA: BEGIN OF ITAB OCCURS 0.
        INCLUDE STRUCTURE IDOCSYN.
DATA: END OF ITAB.
SELECT A~IDOCTYP " Basic type
       B~NR      " Sequential Number of Segment in IDoc Type
       B~SEGTYP " Segment type
       B~PARSEG " Name of parent segment
       B~PARPNO " Sequential number of parent segment
       B~PARFLG " Flag for parent segment: Segment is start of segment
                                                             " group
       B~MUSTFL " Flag: Mandatory entry
       B~OCCMIN " Minimum number of segments in sequence
       B~OCCMAX " Maximum number of segments in sequence
       B~HLEVEL " Hierarchy level of IDoc type segment
       INTO TABLE ITAB
       FROM EDBAS AS A INNER JOIN
            IDOCSYN AS B
        ON AIDOCTYP EQ BIDOCTYP.
SORT ITAB BY IDOCTYP NR." Sort the idoctype and according the segment "
                        "number for the right order in the basic idoc
                        "syntax.
LOOP AT ITAB.
AT NEW IDOCTYP.
      WRITE:/ '***********'.
      WRITE:/1 ITAB-IDOCTYP.
ENDAT.
     WRITE:/.
     SY-COLNO = 5 + ( ITAB-PARPNO * 2 ). " this displays the segments
                                         "under the respective parent
                                         "segments.
     WRITE AT SY-COLNO ITAB-SEGTYP.
ENDLOOP.
Thank you.

Incomplete Idoc received in SAP R/3

Hi XI Gurus
I am working on a File to Idoc scenario and stuck because of a strange issue.
The output Idoc structure sent from XI and as viewed in IDX5 / SXMB_MONI is as below
<?xml version="1.0" encoding="UTF-8"?>
<ACC_DOCUMENT01>
 <IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1">
 <SNDPRT>LI_SND</SNDPRT>
 <SNDPFC>LF_SND</SNDPFC>
 <SNDPRN>0000000100</SNDPRN>
 </EDI_DC40>
 <E1BPACHE09 SEGMENT="1">
 <OBJ_TYPE>BKPFF</OBJ_TYPE>
 <OBJ_KEY>PR2000627830002007</OBJ_KEY>
 <OBJ_SYS>T47CLNT800</OBJ_SYS>
 <BUS_ACT>RFBU</BUS_ACT>
 <USERNAME>lovein</USERNAME>
 <COMP_CODE>3000</COMP_CODE>
 <DOC_DATE>2007-09-11T05:18:52-07:00</DOC_DATE>
 <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
 <DOC_TYPE>SA</DOC_TYPE>
 </E1BPACHE09>
 <E1BPACCAHD/>
 <E1BPACGL09>
 <ITEMNO_ACC>1</ITEMNO_ACC>
 <GL_ACCOUNT/>
 <ACCT_TYPE>S</ACCT_TYPE>
 <DOC_TYPE>SA</DOC_TYPE>
 <COMP_CODE>3000</COMP_CODE>
 <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
 <VENDOR_NO/>
 </E1BPACGL09>
 <E1BPACAP09>
 <ITEMNO_ACC>00001</ITEMNO_ACC>
 <VENDOR_NO/>
 <COMP_CODE>3000</COMP_CODE>
 <PYMT_METH>ach</PYMT_METH>
 </E1BPACAP09>
 <E1BPACCR09>
 <ITEMNO_ACC>1</ITEMNO_ACC>
 <CURR_TYPE>00</CURR_TYPE>
 <CURRENCY>USD</CURRENCY>
 <CURRENCY_ISO>USD</CURRENCY_ISO>
 <AMT_DOCCUR>-30000</AMT_DOCCUR>
 </E1BPACCR09>
 <E1BPACCR09>
 <ITEMNO_ACC>Constant</ITEMNO_ACC>
 <CURR_TYPE>00</CURR_TYPE>
 <CURRENCY>USD</CURRENCY>
 <CURRENCY_ISO>USD</CURRENCY_ISO>
 <AMT_DOCCUR>0</AMT_DOCCUR>
 </E1BPACCR09>
 <E1BPACCR09>
 <ITEMNO_ACC>Constant</ITEMNO_ACC>
 <CURR_TYPE>00</CURR_TYPE>
 <CURRENCY>USD</CURRENCY>
 <CURRENCY_ISO>USD</CURRENCY_ISO>
 <AMT_DOCCUR>30000.00</AMT_DOCCUR>
 </E1BPACCR09>
 </IDOC>
</ACC_DOCUMENT01>
But the Idoc received in SAP R/3 as viewed in Transaction WE02 or table EDID4 has only one node E1BPACHE09
and because rest of the nodes are missing SAP R/3 fails to process the Idoc .
Any help to analyse the issue will be highly appreciated.
Thanx
Lovein

Hi Lovein,
What you can do is:
1. Go to SXMB_MONI and take the output xml.
2. Now go to your mapping under TEST tab and test the above mentioned output xml and see what is the output, i mean are you able to see all the desired output as per you mapping or not.
3. If not then probabily you will get an error message, then try to find out the solution in your mapping only.
4. If you are not able to do that, kindly send the error message, which you got in mapping.
I hope this will solve your issue.
Regards,
Sarvesh
****Reward points, if found helpful.

Info IDoc received with status 8 in BI but Data available in source system

Hello Experts,
I am loading Budget Period (attributes) into PSA in BI.
Budget Period data Loading Issue : No data available while loading. But source system ie ECC has data in that data source
Data source: 0PU_BDGTID_ATTR
This is full load.
I checked that whether I am making any mistake during data selection. I could not find any issue. Message while loading data into PSA (Yellow Traffic light)
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Already looked this thread and googled also.
Re: IDoc received with status 8.
Check points:
sm58 - NO issue
BD87 in ECC (RSINFO Idoc status: 03) -sucessful
BD87 in BI (RSINFO Idoc status : 53)
ST22 - NO issue
sm37 - Job is successful (I could see Idoc no in ECC source system in Job log)
I am not sure if I am missing any thing.
Thanks
Rana

Hi all,
I've got exactly the same issue with several extractors. I'm inialising the Master Data in a all new system, in the Quality the loads succeeded but in Prod it failed.
For instance with the basic DataSource "0FUNCT_LOC_TEXT", I've made the following test:
RS3 (R/3) - > 0 data
ST22 -> no short dump
WE05 (Idoc) - > everything is ok
I reactivated the Datasource in R/3 (RSA5) and then deleted it and replicated it in BW but the same issue occured.
Any ideas?
Thanks
jak

Basic Idoc Adapter Error - XI 3.0

Hi,
I am new to XI so excuse me if this is a basic question.
The scenario we have is File -> XI -> IDOC
When the message is processed into the IDOC Adapter I am getting the following error :
Control record must start with tag EDI_DC40 not E1LFA1M
Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
Is there something I need to change in the Idoc Adapter to get this to happen ?
Kind regards
colin.

It is not a basic question, but it seems to be a common problem.
Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
Regards
Stefan

Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
Could you please tell me , what is the issue with the partner type configuration .

Hi,
Error 29 occurs when there is an incomplete or no partner profile maintained.
Check whether you have done the correct partner profile settings in WE20 outbound parameters.
For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
with correct message type WMMBXY and Idoc type WMMBID02. Also check for message function code.
Regards,
Savitha

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Extension of BASIC IDoc

Hi,
can any body tell me , what are the steps of BAsic IDoc extension,
Regards,
Bhaskar

Hi..
These are the Steps to Enhance IDOC Type:
IDOC EXTENSIONS
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, letâs determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX .Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX .
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application. It may be necessary to enhance an ALE function module even in situations where an IDOC extension has not been performed if the IDOC data being passed to and from the application requires modifications. The following approach applies to both situations.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
The point in the ALE function module where the function exit occurs
The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Reward if Helpful.

Speed connections Issues Help?

Hi,
New to the forum and looking to receive any help with my problem.
Background Info:
I was on sky broadband and receiving a steady 4mbs D/L (Up to MB +Unlimited Broadband) at £12 per month.
A BT Representative cold called me and persuaded me to switch the broadband to BT (Already have the Phone with BT).
I was informed that i would get at least MB d/l and up to MB - so signed for the option 1.
Then I realized that my household is a heavy user,so changed the package to option 3 (Unlimited Broadband Usage)
costing me an instant £21.80 bill for adjustments.Fair enough.
The Problem:
After the 10 day period I am only getting 2.MB D/l at best.
I have been on the phone with BTU+their team of specialists and have still not resolved the issues as of yet.
I have to call back on Saturday after leaving the router on for a further 48 hours without powering down.
So Basically:
Paying twice as much for only half of what i was getting with sky?
If I could cancel the lot and switch back to sky .I would!
Rant Over (for now)
Thanks
Paul
Solved!
Go to Solution.

welcome to the forum
in order for the forum members to help please can you post the adsl stats from your router may need to 'show detail' to get all stats (if hub enter 192.168.1.254 in your browser and navigate to adsl or use a-z, if netgear enter 192.168.0.1) and run btspeedtester (MAC users may have problems) http://speedtester.bt.com or http://bt.custhelp.com/app/answers/detail/a_id/9354/c/346,4740,5520 and post the results .
are you connected directly to the NTE5 master or test socket or to somewhere else? Do you have any phone extension sockets in your home?
Have you tried the quiet line test? - dial 17070 option 2 - should hear nothing - best done with a corded phone. if cordless phone you may hear a 'dull hum' which is normal
Someone may then be able to offer help/assistance/suggestions to your problem
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Questions you need to answer to receive better help

Questions you need to answer to receive better help... please answer as much as you can, that relates to your problem, back in your original message
If a program is not showing on the Cloud screen, it is most likely because your computer does not meet the specifications
FOR EXAMPLE, Premiere Pro requires a 64bit computer - Not all apps displayed for download | Creative Cloud desktop app, Adobe Application Manager
What error message do you see, or what is the screen you see that does not work? (examples... a BLANK login screen, or a spinning wheel)
A screen shot works well to SHOW people what you are doing - http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
Are you using Windows or Mac, and exactly which version? (include "dot" numbers like Windows 8.1 or Mac 10.9.3)
Which brand and version web browser are you using... and have you tried a different web browser?
What Firewall do you use, and have you tried turning it off to download?
What anti-virus do you use, and have you tried turning it off to download?
Has this ever worked before? If yes, do you recall any changes you made to the program, such as adding Plug-ins, etc.?
Did you make any changes to your system, such as updating hardware, printers or drivers; or installing/uninstalling any programs since this last worked?
Are you using an account with Administrator Privileges? Run as Administrator will sometimes help (this EXAMPLE http://forums.adobe.com/thread/969395 is for Encore + "All" Premiere)
What were you doing when the problem occurred?
What other software are you running?
Tell us about your computer hardware. How much RAM is installed? How much free space is on your system (C:) drive?
Hardware Blue Screen shutdowns http://forums.adobe.com/thread/1427408?tstart=0
For Windows, do NOT rely on Windows Update to have current driver information
(you need to go direct to the vendor web site and check updates for yourself)
What is your exact brand/model graphics adapter (ATI or nVidia or ???)
What is your exact graphics adapter driver version?
Have you gone to the vendor web site to check for a newer driver?
ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
Do you have dual graphics adapters? (common in many "energy saving" laptops)
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-and a Mac Utility http://forums.adobe.com/thread/1017891?tstart=0
JUST FOR MAC USERS
Next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-Mac 10.9.3 and CS6 https://forums.adobe.com/thread/1480238
Enable Mac Root User https://forums.adobe.com/thread/1156604
-more Root User http://forums.adobe.com/thread/879931
-and more root user http://forums.adobe.com/thread/940869?tstart=0
Case sensitive hard drive
-http://helpx.adobe.com/creative-suite/kb/error-case-sensitive-drives-supported.html
Troubleshooting guide for Mac freeze
-http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
Some links concerning error codes
http://helpx.adobe.com/creative-cloud/kb/failed-install-creative-cloud-desktop.html
A12... download & install error http://forums.adobe.com/thread/1289484
-more A12... discussion http://forums.adobe.com/thread/1045283?tstart=0
U44.. update error http://forums.adobe.com/thread/1289956 may help
-more U44.. discussion http://forums.adobe.com/thread/1275963
-http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
-http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html
http://helpx.adobe.com/x-productkb/global/installation-launch-log-errors-creative.html
Repeated updates http://helpx.adobe.com/creative-cloud/kb/updates-repeatedly-applied-cc.html
Code 6 & Code 7 http://helpx.adobe.com/creative-suite/kb/errors-exit-code-6-exit.html
Error 16 http://helpx.adobe.com/x-productkb/policy-pricing/configuration-error-cs5.html
-including DW039 https://forums.adobe.com/thread/1500609
Error 49 https://forums.adobe.com/thread/1491394
Error 50 https://forums.adobe.com/thread/1432237
Errors 201 & 205 & 206 & 207 or several U43 errors
-http://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html
Muse error http://helpx.adobe.com/muse/kb/unexpected-error-occurred-i-200.html
InDeisgn error http://helpx.adobe.com/indesign/kb/indesign-cc-crashing-launch.html
Sign Out When Sign In http://forums.adobe.com/thread/1450581?tstart=0 may help
-and http://helpx.adobe.com/creative-cloud/kb/unable-login-creative-cloud-248.html
-and 'looping' https://forums.adobe.com/thread/1504792
BLANK Cloud Screen http://forums.adobe.com/message/5484303 may help
-and step by step http://forums.adobe.com/thread/1440508?tstart=0
-and http://helpx.adobe.com/creative-cloud/kb/blank-white-screen-ccp.html
Mac Spinning Wheel https://forums.adobe.com/message/5470608
-Similar in Windows https://forums.adobe.com/message/5853430

Does anyone know if there's a way to change the questions themselves? (Frankly, they have to be the most ridiculous security questions I've ever seen. A good security question should be one that you'll have no problem remembering the answer to, even if you're asked years later. To answer one from the third batch, I'd have to make something up, which makes it unlikely I'll remember the answer later. And I certainly don't want to have to write the answers down somewhere.)

IP Job in BW finished, but how can I check the IDoc receive status in BW ?

Hi,experts
After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
and how can I do now ? or how can I check the IDoc receive status in BW side?

Hi,
I too had the same problem, i executed the following to solve the proble, may be this will help you:
1) Go to T-code SM58 and select TRFC and press F6,
2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
Thanks,

Performance problem in IDoc receive (DELFOR01)

Hi,
I have serious problems in receive of Idoc Delfor01 (IDOC_INPUT_DELINS). We receive more than 3000 Idoc daily of this type and the process of then during all day....
One of more common error is foreing_lock of VBAK table. This error occurs in the Form beleg_sperren (line 459 from IDOC_INPUT_DELINS) when the process try enqueue one vbeln entrie from VBAK (o think by the high number of Idoc received) and, the process waits a large time trying enqueue the table entry until the error...
When I analyze the IDOC_INPUT_DELINS i see a batch-input for the VA32 transaction (at line 528). I think if call a Bapi instead a Call Transaction have more performance... it´s right?
I would appreciate help with possible solutions to this problem.. Have a better mode to process large amount of these IDoc type? Or have other FM than IDOC_INPUT_DELINS with better performance???
Regards,

Not need immediatly, but a quickly possible... In WE20 if I choose the background program the process will executed* fastly than I choose Imediattly start?
*executed via schedule job of program RBDAPP01.
I stil reading the notes above..

Adobe Media Encoder Issue Help

Hello all,
I am having an issue with Adobe Media Encoder that I am hoping to receive some help with. I am rendering out some videos from Premiere and every time I render something larger than 1 GB, I receive this error message:
"Adobe Media Encoder
Could not write XMP data in output file."
It has only started since the last update about a month ago, so any help would be greatly appreciated!
Thanks again!

Any help please?! Thank you!

A problem about IDOC Receiver

Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.

Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
recipient port the port created in step (2)
recipient partner number the logical system name of the dotnet application created in (2)
recipient partner type'LS'
sender port SAP<SID>, where SID is the SAP system id
sender partner number the logical system name the SAP client maintained in step step (4)
sender partner type'LS'
message type the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
Willy

Basic IDOC Receiver Issues - help

Similar Messages

Maybe you are looking for