Triggering IDoc from SE38

hi,
i am triggering IDoc to XI from my report in ABAP.
when i am filling the control record in the report , the value for the RCVPRN i.e receiver partner should be determined from the partner profiles and should not be hard coded in the report.
how do i achieve this .
kindly help
very urgent
regards ,
loveena

HI,
You can do this with ABAP report.
Please refer the table EDP21---Partner Profile: Inbound
Here all the message types for the Logical system are maintained.
From this you could get the RCVPRN values. The field SNDPRN contains the values of RCVPRN.
But here one Message type can be available with multiple RCVPRN values. So in ABAP code you need to handle as per requirment.
Thanks
Swarup

Similar Messages

Triggering IDoc from R3 using variant program

Hi,
I am using the variant program to trigger the IDoc from R/3 System.
It is successful in r/3 system but its not reaching in XI.
Help me in resolving this issue.
Regards,
Inder

do you find any trace in SM58 ?
Check if there are proper authorizations for the user in the destination.
For authorization;
Authorization object S_RFC
Field name RFC_TYPE value FUGR
Field name RFC_NAME value EDIMEXT, SDTX
Field name ACTVT    value 16
Authorization object S_IDOCDEFT
Field name ACTVT   value 03
Field name EDI_CIM value ' '
Field name EDI_DOC value TXTRAW01
Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
Field name ACTVT      value 03
Field name DICBERCLS value

Re-triggering Idocs from SAP Communication layer

Hi,
Our webmethods middleware went down for 4 hours. We are trying to see if there is a quick way to retrigger Idocs from SAP for around 3000 doc (various doc, PO, SO, Delivery, Shipment etc). Trying to see if we can change the status in SAP and retrigger (without writing a program). Is there a way to do it. Any pointers would be useful.
Thanks,
Anand

There is no quick way to resend IDocs that have already passed. I worked at a client in the past that had written a custom program to change the status of an IDoc. The report program had a similar selection screen to WE05, but current status and new status as parameters. The program would retrieve IDocs based on the selection criteria and update EDIDC-STATUS to '30'. You can then resend the IDocs using RSEOUT00.
You do not need to modify EDIDS.

Triggering idoc from ECC to XI

I have a idoc-xi-jms scenario where
I have a matrial master, and whenever I change sth in it idoc got to be triggered from ECC with change pointer logic.
I have changed 2 materials and when I ran the RBDMIDOC Program manually, surprisingly some 20000 idocs are triggered.
Can somebody advise me how can I avoid this typical problem if I want to send only changed materials ( i.e only 2 idocs) ??
Thanks
kumar

the change pointer program ususally accumlates all the changes ad then sends them out....
chk the tables CDHDR and CDPOS for changes usually before you trigger the RBDMIDOC program.
Also you can create use the enhancement spot to create a custom code which deletes the changes caused by other criteria than wht you are looking for.
Hope this helps!!
Cheers!!
Sidharth

Problem while triggering IDoc

hi,
When i am triggering idoc from R/3 , it is saying idoc transferred to port,
but when i am checking the idoc in XI system idx5 , i am not able to view the idocs,
What could be the reason for this?
Also when i am creating distribution model in BD64 and then saying distribute , it is giving this message:
Model view BANK_CREAT has not been updated
Reason: Maintenance systems for model view BANK_CREAT are not identical
..... Maintenance system in sending system DMYCLNT702
..... Maintenance system in receiving system DMYCLNT100
Note:DMYCLNT702 - Testing client
DMYCLNT100 - Development
Urgent help needed,
Thanks,
Loveena

Hi,
Chk the following details which will be helpful:
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Also chk the following link providing details of pushing idocs:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Regarding Triggering the job from se38

When i trigger a job from se38, i get a message saying " Event or Parameter has been raised on the server " can any one make me understand what does it mean.

Hi
SE38 functions are,
    Create variants
     Display variant directory
     Display and change values and attributes
     Copy, delete and rename variants.
Find the link below,
http://help.sap.com/saphelp_nw04/helpdata/en/c3/67ee407552742ae10000000a155106/frameset.htm
I think this will help you,
Regards
Sibvanand

How to Trigger an IDOC from SAP R/3 to two systems at a time

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
Can any one tell me how can we do that ?
Regards
Ram.

Hello Ram,
Do you have connectivity between your production & XIQ?
What does "connectivity" mean?
1. RFC destination is maintained.
2. Port defined for the RFC destination.
If no, create these. (Search in SDN for details).
If yes, proceed:
1. Define the logical system for XIQ.(BD54)
2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
3. Create a distribution model view with sender as "your production" & receiver as XIQ.
3.1. Add the messages which you want to distribute.
3.2 Generate Partner profiles.
No coding is reqd. for this.
BR,
Suhas

How to trigger an Idoc from Sales order creation and change

We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
Follow the below steps:
1. Go to NACE transaction
2. Select V1 application and select OUTPUT TYPES
3. Select the required output type and double click on Processing routines.
4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
5. Save it.
message type ORDERSP in the distribution model (BD64).
Follow the below steps to configure the condition records:
1. Go to NACE
2. Select V1 application and select CONDITION RECORDS
3. Select the requred output type and click on Condition records
4. Selection screen will be displayed.
5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
Sales doc type = OR
Funt = SP
Partner = blank. It means there is no restriction on partner numbers.
Medium = A
date/time = 4
Lan = EN.
Note: partner is left blank means, the sales order of type OR can be send to all partners.
6. Save it.
We also done ALE configuration.
We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
Kindly suggest the solution.
Regards,
Sharad Dixit

Hi ,
Please check the total error description and diagnosis as below :
InVa02 enter SO go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
Please paste the diagnosis .
Thanks and Regards,
P.Bharadwaj

Creation of Idocs from the change pointers by the program RBDMIDOC

Hello,
I'm Creating Idocs from the change pointers by the program RBDMIDOC.
The IDOCS Created using the message type HRMD_A are Correct but when i try to RUN RBDMIDOC for message type HRMD_B no Data is selected for distribution.
All the customizing are similar and i presume that all the change pointers are active (BD50 and IMG->Personnel Management -> Organizational Management -> Basic Settings -> Activate change documents).
Can anyone help me with the necessary steps to create this IDOC types.
Do anyone know if the RBDMIDOC report is the Same for messages HRMD_A and HRMD_B.
Thanks in Advance,
Pedro Ferreira

If the setting is fine, there may be some code in exit or badi for program RBMIDOC. Check the Exit and BADI.
check the exit EXIT_SAPLBD11_001 and
check the badi IDOC_CREATION_CHECK.
Probably there may be some code on these exits which are stoping your code from getting generated.These are the two trigger happen once u execute the RBMIDOC program.for HR, we use RHALEINI program to generate the idoc. but even RBDMIDOC works. These 2 triggere will come with RHALEINI also.
If there is no code here, Then there is problem in the setting only.

Help needed in transferring IDoc from SAP CRM to XI

Hi All,
We are facing an issue in sending an IDoc from SAP CRM to XI system. The IDoc is triggered and the status is showing as 03 in SAP CRM system(WE05 is used) but it is not getting replicated in XI System. This is verified by logging into XI System and cross checked the records retrieved by executing the transaction IDX5. No entry is found for this IDoc.
In SM58 transaction, it is giving the status text as EDISDEF:Port SAPRIO segment defn E201CRMXIF_BILLI.
Any pointers on this issues will be very helpful. We are able to send information from XI to CRM.
The project is an upgrade one and the IDocs are developed earlier and were working fine one week back and no changes were made recently.
Thanks,
Udaya

Hi Kapil,
Thanks a lot for your help. We need to delete and recreate Metadata. This is a typical problem that is encountered during upgrade projects.
Thanks,
Udaya

How to Trigger an IDOC from SAP R/3 to two XI systems

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELCERY01 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once.
Regards
Ram.

Hi Ravi,
Thank you very much for your answer.
As I am not completely aware of R/3 side,I am getting little problem in understanding your answer.
Could you please explain the same in some what beter way.. Thank you ..

Unable top convert the status of idoc from 03 to 12

Hi experts,
I am working on idoc scenario on ECC6.0.I am pushing the idoc from R/3 system to PI7.0.I have done all the prerequisites involved to pushing idoc-----
maintain Rfc destinations,maintain port,partner profile,distribution model....
But when i am pushing the reduced idoc from sender it's showing the status 03.when i am running RBDMOIND in se38 still it is not getting converted into 12.
kindly help me how can I convert the status from 03 to 12.
Thanks in advance.
Regards,
Naresh.K

Hi Naresh
you have to create the service. Create first the technical system and the business system in the SLD. Look for the right "Logical System" (Transation SALE in R3).
In the Integration Builder Directory go to "Environment/Clear SLD Data" and create the service by "Objects/Service without party/Business System/Assign Business System".
Hope this will solve your Querry
Thanks !!
Questions are welcome here!!
Also mark helpful answers by rewarding points 
Regards
Abhishek Agrahari

Want to transfer data via idocs from one R/3 to different R/3

Hi!!
May i hav nay step by step pdf which gives the complete flow of how to transfer idocs from from one R/3 to different R/3.
Though i have the basics steps but some where I m stuck.
Also I have two doubts::
1.Is thr Any relation bw port name and Logical System name?Can they be same.??I hav kept Logical System name as SAPE60 AND PORT name also as SAPE60(in e60) and SAPEI6(in ei6) servers respectively.
2.Should the Logical System names be maintained same in both the servers??
Kindly respond .
Helpful answers will be rewarded points!!!

Hi Deepika ,
See the Example scenarios
MASTER DATA TRANSFERMATION BETWEEN 2 DIFF CLIENTS
 For this scenario Client 800 is the Sender and 810 is the receiving system
1. Creating Logical Systems
o Login using 800 client
o Go to T. Code SALE
o Expand Sending and Receiving Systems
o Expand Logical Systems
o Click on Define Logical System
o Click on New Entries
o Create STUD_S, STUD_R Logical Systems
o Save and come back
o Assign the STUD_S Logical System to client 800
o Assign the STUD_R Logical System to client 810
2. Creating the RFCs
o Go to T. Code SM59
o Expand R/3 Connections
o Enter RFC Name as STUD_S
o Connection Type as 3
o Language as EN
o Client as 800
o User as SAPUSER
o PWD as abap
o Target host as sap
o Click on Remote logon button to test the RFC
o Enter RFC Name as STUD_R
o Connection Type as 3
o Language as EN
o Client as 800
o User as SATISH
o PWD as abap
o Target host as sap
o Click on Remote logon button to test the RFC
3. Creating the Message Type
o Go to T. Code WE81
o Click on change, continue
o Click on New Entries button
o Give message type as ZBAPI_STUD_MAS and description
o Save and back
4. Creating the Segment
o Go to T. Code WE31
o Give segment name as ZBAPI_STUD_SEG
o Enter Short Text
o Enter the Field Name and Data Element in the text boxes
o Save, continue,
o Click on Edit -> Set Release.
5. Creating the Basic IDOC Object
o Go to T. code WE30
o Give obj. name as ZBAPI_STUD_IDOC
o Click on create
o Select create new radio button, give description and continue
o Select the IDOC obj name and click on create button
o Enter the segment name which is create earlier
o Select the check box if you want to make the segment mandatory
o Enter 1 in minimum number 99999 in maximum number, continue
o Save and back
o Click on Edit -> Set Release
6. Creating Customer Distribution Model
o Go to T. Code BD64
o Click on change and Create model view button
o Enter the short text and Technical name as ZSTUDENT
o Select the model and click on Add Message Type Button
o Give the Sender as STUD_S,
o Receiver as STUD_R,
o Message Type as ZBAPI_STUD_MAS
o Select the model view & click on Environment -> Generate Partner Profiles
o Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o Click on Execute
o You should get a list in green color which means it executed successfully.
o Back to main screen, select the model view
o Click Edit->Model view->Distribute
o Click on continue
o You should get a list saying model view is distributed successfully.
7. Checking the Port
o Go to T. Code WE21
o Expand Transactional RFC
o Find the port from the list which is created using BD64 for STUD_R (Receiving system) RFC Destination.
8. Checking the Partner Profiles.
o Go to T. Code WE20
o Expand Partner Type LS
o Select the Partner profile STUD_R
o Double click on Message Type ZBAPI_STUD_MAS in Outbound parmtrs.
o Check Receiver Port is assigned correctly
o Check the Basic type as your Basic IDOC object.
9. Assigning the Message Type to Basic IDOC Object
o Go to T. Code WE82
o Click on Change & continue, New Entries button
o Give the Message type as ZBAPI_STUD_MAS
o Give Basic Type as ZBAPI_STUD_IDOC
o Release as 46C
o Save and back
10. Creating Inbound Function Module (Posting Program)
o Go to T. Code SE37
o Create a function Module IDOC_INPUT_ZBAPI_STUD_MAS
o Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.
o Import Parameters
INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD
MASS_PROCESSING LIKE BDWFAP_PAR-MASS_PROC
NO_APPLICATION_LOG LIKE SY-DATAR
MASSSAVEINFOS LIKE MASSSAVINF
o Export Parameters
WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT
APPLICATION_VARIABLE LIKE BDWF_PARAM-APPL_VAR
IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK
CALL_TRANSACTION_DONE LIKE BDWFAP_PAR-CALLTRANS
o Tables
IDOC_CONTRL LIKE EDIDC
IDOC_DATA LIKE EDIDD
IDOC_STATUS LIKE BDIDOCSTAT
RETURN_VARIABLES LIKE BDWFRETVAR
SERIALIZATION_INFO LIKE BDI_SER
o Exceptions
WRONG_FUNCTION_CALLED
o Source Code
DATA: FIRST_TRANC LIKE MARA_UEB-TRANC,
 ZBAPI_STUD_SEG like zbapi_stud.
DATA: ZBAPI_STUD LIKE ZBAPI_STUD.
DATA: I_ZBAPI_STUD LIKE ZBAPI_STUD.
DATA: C_TRUE VALUE 'X'.
DATA: C_FALSE VALUE ' '.
DATA: BEGIN OF T_IDOC_ROLLNO OCCURS 0,
 DOCNUM LIKE EDIDC-DOCNUM,
 ROLLNO LIKE ZBAPI_STUD-ROLLNO,
 END OF T_IDOC_ROLLNO.
DEFINE APPEND_RESFIELDS.
 PERFORM APPEND_RES_FIELDS TABLES T_MFIELDRES
 T_RES_FIELDS
 USING &1
 COUNTER-D_IND.
END-OF-DEFINITION.
DATA: I_MARA_UEB LIKE MARA_UEB.
DATA: I_ZSTUD_UEB LIKE ZBAPI_STUD.
DATA: I_MAKT_UEB LIKE MAKT_UEB.
DATA: I_MARC_UEB LIKE MARC_UEB.
DATA: I_MARD_UEB LIKE MARD_UEB.
DATA: I_MFHM_UEB LIKE MFHM_UEB.
DATA: I_MARM_UEB LIKE MARM_UEB.
DATA: I_MEAN_UEB LIKE MEA1_UEB.
DATA: I_MBEW_UEB LIKE MBEW_UEB.
DATA: I_STEU_UEB LIKE STEU_UEB.
DATA: I_STEUMM_UEB LIKE STEUMM_UEB.
DATA: I_MLGN_UEB LIKE MLGN_UEB.
DATA: I_MLGT_UEB LIKE MLGT_UEB. " //br010797 neu zu 4.0
DATA: I_MPGD_UEB LIKE MPGD_UEB.
DATA: I_MPOP_UEB LIKE MPOP_UEB.
DATA: I_MVEG_UEB LIKE MVEG_UEB.
DATA: I_MVEU_UEB LIKE MVEU_UEB.
DATA: I_MVKE_UEB LIKE MVKE_UEB.
DATA: I_MPRW_UEB LIKE MPRW_UEB.
DATA: I_LTX1_UEB LIKE LTX1_UEB.
DATA: HELP_MARC_UEB LIKE MARC_UEB.
DATA: T_MARA_UEB LIKE MARA_UEB OCCURS 0.
DATA: T_MAKT_UEB LIKE MAKT_UEB OCCURS 0.
DATA: T_MARC_UEB LIKE MARC_UEB OCCURS 0.
DATA: T_MARD_UEB LIKE MARD_UEB OCCURS 0.
DATA: T_MFHM_UEB LIKE MFHM_UEB OCCURS 0.
DATA: T_MARM_UEB LIKE MARM_UEB OCCURS 0.
DATA: T_MEAN_UEB LIKE MEA1_UEB OCCURS 0.
DATA: T_MBEW_UEB LIKE MBEW_UEB OCCURS 0.
DATA: T_STEU_UEB LIKE STEU_UEB OCCURS 0.
DATA: T_STEUMM_UEB LIKE STEUMM_UEB OCCURS 0.
DATA: T_MLGN_UEB LIKE MLGN_UEB OCCURS 0.
DATA: T_MLGT_UEB LIKE MLGT_UEB OCCURS 0. " //br010797 neu zu 4.0
DATA: T_MPGD_UEB LIKE MPGD_UEB OCCURS 0.
DATA: T_MPOP_UEB LIKE MPOP_UEB OCCURS 0.
DATA: T_MVEG_UEB LIKE MVEG_UEB OCCURS 0.
DATA: T_MVEU_UEB LIKE MVEU_UEB OCCURS 0.
DATA: T_MVKE_UEB LIKE MVKE_UEB OCCURS 0.
DATA: T_MPRW_UEB LIKE MPRW_UEB OCCURS 0.
DATA: T_LTX1_UEB LIKE LTX1_UEB OCCURS 0.
Internal fields/ tables
DATA: FLAG_ERROR_HAPPENED.
DATA: flag_material_exists. "//br210397 zu 4.0 keine Verwendung mehr
DATA: FLAG_EXIT_TO_BE_DONE.
DATA: HELP_TABIX LIKE SY-TABIX.
DATA: HELP_TRANC LIKE MARA_UEB-TRANC.
DATA: HELP_ALAND LIKE STEU_UEB-ALAND.
DATA: HELP_VKORG LIKE MVKE-VKORG.
DATA: HELP_WERKS LIKE T001W-WERKS.
DATA: HELP_LFDNR LIKE STEU_UEB-LFDNR.
DATA: LAST_MARC_TRANC LIKE MARA_UEB-TRANC.
DATA: LAST_MLGN_TRANC LIKE MARA_UEB-TRANC. " //br010797 neu zu 4.0
DATA: LAST_TEXT_TRANC LIKE MARA_UEB-TRANC.
DATA: CURRENT_TABIX LIKE SY-TABIX.
DATA: GENERAL_SUBRC LIKE SY-SUBRC.
DATA: HELP_FACTOR TYPE P DECIMALS 3.
DATA: USER_SEGMENTS LIKE EDIDD OCCURS 0 WITH HEADER LINE. " insert
DATA: CUST_SEGMENT LIKE EDIDD.
DATA: I_MFIELDRES LIKE MFIELDRES.
DATA: I_MERRDAT LIKE MERRDAT.
DATA: I_EDIDD LIKE EDIDD.
 " //br neu zu 3.1g
DATA: T_RES_FIELDS LIKE DELFIELDS OCCURS 0 WITH HEADER LINE.
DATA: T_MFIELDRES LIKE MFIELDRES OCCURS 0.
DATA: T_MERRDAT LIKE MERRDAT OCCURS 0.
DATA: T_EDIDD LIKE EDIDD OCCURS 0.
DATA: BEGIN OF t_matnr OCCURS 0, "//br210397 zu 4.0
 matnr LIKE mara-matnr, " wird nicht mehr verwendet
 END OF t_matnr. "
DATA: BEGIN OF COUNTER,
 TRANC LIKE MARA_UEB-TRANC,
 D_IND LIKE MARA_UEB-D_IND,
 END OF COUNTER.
DATA: BEGIN OF t_idoc_tranc OCCURS 0, " 4.0
 docnum LIKE edidc-docnum, "
 tranc LIKE mara_ueb-tranc, "
 END OF t_idoc_tranc. "
DATA T_IDOC_TRANC LIKE MATIDOCTRANC OCCURS 0 WITH HEADER LINE."
DATA: FLAG_FITS.
DATA: APPLICATION_SUBRC LIKE SY-SUBRC.
DATA FLAG_MUSS_PRUEFEN LIKE SY-DATAR.
DATA MAX_ERRORS LIKE T130S-ANZUM. " 4.0
note 419281
DATA : FLG_MASS.
CLEAR : FLG_MASS.
FIELD-SYMBOLS: . " 4.0
ALE-distribution unity : IDOC status set by locking "note0361838
data: "note0361838
 it_dsp_idocstat like bdidocstat "note0361838
 occurs 0 with header line. "note0361838
Initialize data - general
REFRESH T_MFIELDRES.
REFRESH T_IDOC_TRANC.
REFRESH T_IDOC_TRANC. "JH/02.02.98/4.0C KPr100004993
REFRESH t_idoc_tranc_segment. " //br 40 : unnötig
REFRESH matnr_tranc. " -"-
REFRESH t_matnr.
COUNTER-TRANC = 1.
COUNTER-D_IND = 1.
REFRESH T_MARA_UEB.
REFRESH T_MAKT_UEB.
REFRESH T_MARC_UEB.
REFRESH T_MARD_UEB.
REFRESH T_MFHM_UEB.
REFRESH T_MARM_UEB.
REFRESH T_MEAN_UEB.
REFRESH T_MBEW_UEB.
REFRESH T_STEU_UEB.
REFRESH T_STEUMM_UEB.
REFRESH T_MLGN_UEB.
REFRESH T_MLGT_UEB. " //br010797 neu zu 4.0
REFRESH T_MPGD_UEB.
REFRESH T_MPOP_UEB.
REFRESH T_MVEG_UEB.
REFRESH T_MVEU_UEB.
REFRESH T_MVKE_UEB.
REFRESH T_MPRW_UEB.
REFRESH VKORG_ALAND.
REFRESH WERKS_ALAND.
CLEAR APPLICATION_SUBRC.
REFRESH T_MERRDAT.
Check if right function is called
READ TABLE IDOC_CONTRL INDEX 1.
IF SY-SUBRC <> 0.
 EXIT.
ELSE.
 IF IDOC_CONTRL-IDOCTP <> 'ZBAPI_STUD_IDOC'.
 RAISE WRONG_FUNCTION_CALLED.
 ENDIF.
ENDIF.
LOOP AT IDOC_CONTRL.
Initialize data - per IDOC
t_idoc_tranc-docnum = counter-tranc.
 T_IDOC_TRANC-DOCNUM = IDOC_CONTRL-DOCNUM.
 T_IDOC_TRANC-FIRST_TRANC_IDOC = COUNTER-TRANC + 2.
 APPEND T_IDOC_TRANC.
Select segments which belong to IDOC
 REFRESH T_EDIDD.
 LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
 APPEND IDOC_DATA TO T_EDIDD.
 ENDLOOP.
 BUSINESS TRANSACTION EVENT (header / data) "note0388000
 call function 'OPEN_FI_PERFORM_MGV00200_E' "note0388000
 exporting "note0388000
 idoc_header = idoc_contrl "note0388000
 FLG_APPEND_STATUS = 'X' "note0388000
 tables "note0388000
(DEL) idoc_data = idoc_data "note0388000 note0418561
 idoc_data = t_edidd "note0418561
 idoc_status = idoc_status "note0388000
 exceptions "note0388000
 others = 1. "note0388000
 if sy-subrc = 1. "note0388000
 continue. "note0388000
 endif. "note0388000
Within one IDOC: loop through data segments:
Prepare internal tables for the current material
 LOOP AT T_EDIDD INTO IDOC_DATA.
 Transform from CoreData to Normal Data if necesary
 CASE IDOC_DATA-SEGNAM.
 WHEN 'E1MARAC'.
*--COMMENTED BY SATISH
 PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
 WHEN 'E1MAKTC'.
 PERFORM MOVE_E1MAKTC_TO_E1MAKTM USING IDOC_DATA.
*--COMMENTES ENDED BY SATISH
 WHEN 'ZBAPI_STUD_SEG'.
 PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
 CLEAR I_ZBAPI_STUD.
Second: Move E1MARAC into E1MARAM
 I_ZBAPI_STUD = IDOC_DATA-SDATA.
Third: Move E1MARAM back into IDOC-line
 IDOC_DATA-SDATA = I_ZBAPI_STUD.
 IDOC_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.
 ENDCASE.
 CURRENT_TABIX = SY-TABIX.
 COUNTER-D_IND = COUNTER-D_IND + 1.
 COUNTER-TRANC = COUNTER-TRANC + 2.
 CASE IDOC_DATA-SEGNAM.
 WHEN 'ZBAPI_STUD_SEG'.
 Initialize data - per material
 COUNTER-D_IND = 1.
 FIRST_TRANC = COUNTER-TRANC.
 interpret segment
 ZBAPI_STUD_SEG = IDOC_DATA-SDATA.
 MOVE-CORRESPONDING ZBAPI_STUD TO I_ZSTUD_UEB.
 T_IDOC_ROLLNO-DOCNUM = IDOC_CONTRL-DOCNUM.
 T_IDOC_ROLLNO-ROLLNO = I_ZSTUD_UEB-ROLLNO.
 APPEND T_IDOC_ROLLNO.
 ENDCASE.
 if not ZBAPI_STUD_SEG is initial.
 ZBAPI_STUD-MANDT = ZBAPI_STUD_SEG-MANDT.
 ZBAPI_STUD-ROLLNO = ZBAPI_STUD_SEG-ROLLNO.
 ZBAPI_STUD-FNAME = ZBAPI_STUD_SEG-FNAME.
 ZBAPI_STUD-LNAME = ZBAPI_STUD_SEG-LNAME.
 INSERT ZBAPI_STUD FROM ZBAPI_STUD_SEG.
 COMMIT WORK.
 ENDIF.
*-- ALE ditribution unity : update IDOC status "note03618
 LOOP AT it_dsp_idocstat. "note036
 LOOP AT IDOC_STATUS WHERE DOCNUM = it_dsp_idocstat. "note036
 DELETE idoc_status INDEX sy-tabix. "note036
 ENDLOOP. "note036
 APPEND it_dsp_idocstat TO idoc_status. "note036
 ENDLOOP. "note036
*--GENERATING THE IDOC STATUS
PERFORM HANDLE_ERROR_EXT " //br40
 TABLES "
 IDOC_CONTRL "
 IDOC_STATUS "
 RETURN_VARIABLES "
 T_MERRDAT "
 T_IDOC_TRANC "
 T_IDOC_ROLLNO "JH/4.0C/KPr100004993
 USING "
 GENERAL_SUBRC "
 NO_APPLICATION_LOG "
 MASSSAVEINFOS "wk/40c
 CHANGING "
 WORKFLOW_RESULT. "
 PERFORM HANDLE_ERROR
 TABLES
 IDOC_CONTRL
 IDOC_STATUS
 RETURN_VARIABLES
 T_MERRDAT
 T_IDOC_ROLLNO "JH/4.0C/KPr100004993
 USING
 APPLICATION_SUBRC
 CHANGING
 WORKFLOW_RESULT.
SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124
React on general error
DATA: I_MERRDAT LIKE MERRDAT.
IF GENERAL_SUBRC <> 0.
 I_MERRDAT-MSGTY = 'E'.
 I_MERRDAT-MSGID = SY-MSGID.
 I_MERRDAT-MSGNO = SY-MSGNO.
 I_MERRDAT-MSGV1 = SY-MSGV1.
 I_MERRDAT-MSGV2 = SY-MSGV2.
 I_MERRDAT-MSGV3 = SY-MSGV3.
 I_MERRDAT-MSGV4 = SY-MSGV4.
 APPEND I_MERRDAT TO T_MERRDAT.
ENDIF.
LOOP AT T_MERRDAT INTO I_MERRDAT
 WHERE MSGTY = 'S' "success
 OR MSGTY = 'D' "dummy
 OR MSGTY = 'I' "Information " //br011097 zu 3.1I
 OR MSGTY = 'H' "dummy " 4.0
 OR MSGTY = 'W'. "warning
 DELETE T_MERRDAT.
ENDLOOP.
 ENDLOOP.
ENDLOOP.
ENDFUNCTION.
*& Form handle_error_ext
FORM HANDLE_ERROR_EXT
 TABLES
 IDOC_CONTRL STRUCTURE EDIDC
 IDOC_STATUS STRUCTURE BDIDOCSTAT
 RETURN_VARIABLES STRUCTURE BDWFRETVAR
 T_MERRDAT STRUCTURE MERRDAT
 IDOC_TRANC STRUCTURE MATIDOCTRANC
JH/02.02.98/4.0C KPr100004993 (Anfang)
 T_IDOC_ROLLNO STRUCTURE T_IDOC_ROLLNO
JH/02.02.98/4.0C KPr100004993 (Ende)
 USING
 GENERAL_SUBRC LIKE SY-SUBRC
 NO_APPLICATION_LOG LIKE SY-DATAR
 MASSSAVEINFOS LIKE MASSSAVINF
 CHANGING
 WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT.
DATA FLAG_ERROR_HAPPENED.
DATA I_MERRDAT LIKE MERRDAT.
DATA IDOC_INDEX_2_SUBRC LIKE SY-SUBRC.
DATA AL_HANDLES TYPE BAL_T_LOGH. "//br99
SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124
React on general error
IF GENERAL_SUBRC <> 0.
 REFRESH T_MERRDAT.
i_merrdat-tranc = 0. " //br261197
 READ TABLE IDOC_TRANC INDEX 1. " zu 40b
 I_MERRDAT-TRANC = IDOC_TRANC-FIRST_TRANC_IDOC. "
 I_MERRDAT-MSGTY = 'E'.
 I_MERRDAT-MSGID = SY-MSGID.
 I_MERRDAT-MSGNO = SY-MSGNO.
 I_MERRDAT-MSGV1 = SY-MSGV1. I_MERRDAT-MSGV2 = SY-MSGV2.
 I_MERRDAT-MSGV3 = SY-MSGV3. I_MERRDAT-MSGV4 = SY-MSGV4.
 APPEND I_MERRDAT TO T_MERRDAT.
ENDIF.
DATA: C_TRUE,
 C_FALSE VALUE 'X'.
If error happened ==> Rollback whole work....
LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY NA 'SDHWI'.
 EXIT.
ENDLOOP.
IF SY-SUBRC = 0.
 FLAG_ERROR_HAPPENED = C_TRUE.
 ROLLBACK WORK.
ELSE.
 FLAG_ERROR_HAPPENED = C_FALSE.
ENDIF.
Set IDOC status
two cases:
single IDOC-processing: ==> error can be written in IDOC status
package processing ==> anononymous "package error" for all IDOCs
READ TABLE IDOC_CONTRL INDEX 2.
IDOC_INDEX_2_SUBRC = SY-SUBRC.
IF SY-SUBRC = 0.
 IF 1 = 2. "//br40
 MESSAGE E051(B1). "
 ENDIF. "
 CLEAR I_MERRDAT.
 I_MERRDAT-MSGID = 'B1'.
 I_MERRDAT-MSGTY = 'E'.
 I_MERRDAT-MSGNO = '051'.
ENDIF.
IF IDOC_INDEX_2_SUBRC NE 0 OR FLAG_ERROR_HAPPENED = C_FALSE.
Nur in diesen Fällen wird Application Log geschrieben
Delete all Successes and Dummy records from t_merrdat
DELETE t_merrdat WHERE msgty = 'S' "success " testweise
 OR msgty = 'D'. "dummy "
 LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY = 'D'. "
 I_MERRDAT-MSGTY = 'S'. "
 MODIFY T_MERRDAT FROM I_MERRDAT. "
 ENDLOOP. "
ENDIF.
WORKFLOW_RESULT = 0.
LOOP AT IDOC_CONTRL.
Set IDOC status
 CLEAR IDOC_STATUS.
 IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
 IF FLAG_ERROR_HAPPENED = C_FALSE.
Application log
 PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC
 T_MERRDAT
 IDOC_STATUS
 USING IDOC_CONTRL
 FLAG_ERROR_HAPPENED
 NO_APPLICATION_LOG
 MASSSAVEINFOS
 AL_HANDLES.
 idoc_status-status = '53'. "OK!
 APPEND idoc_status.
JH/02.02.98/4.0C KPr100004993 (Anfang)
 Fill Return variables
 CLEAR RETURN_VARIABLES.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
 APPEND RETURN_VARIABLES.
 Verknüpfungseintrag anlegen
 READ TABLE T_IDOC_ROLLNO WITH KEY ROLLNO = IDOC_CONTRL-DOCNUM
 BINARY SEARCH.
 IF SY-SUBRC = 0.
 RETURN_VARIABLES-DOC_NUMBER = T_IDOC_ROLLNO-ROLLNO.
 RETURN_VARIABLES-WF_PARAM = 'Appl_Objects'.
 APPEND RETURN_VARIABLES.
 ENDIF.
JH/02.02.98/4.0C KPr100004993 (Ende)
 ELSE.
 IF IDOC_INDEX_2_SUBRC NE 0.
Application Log
 PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC
 T_MERRDAT
 IDOC_STATUS
 USING IDOC_CONTRL
 FLAG_ERROR_HAPPENED
 NO_APPLICATION_LOG
 MASSSAVEINFOS
 AL_HANDLES.
 ELSE.
 IDOC_STATUS-MSGID = I_MERRDAT-MSGID.
 IDOC_STATUS-MSGTY = I_MERRDAT-MSGTY.
 IDOC_STATUS-MSGNO = I_MERRDAT-MSGNO.
 IDOC_STATUS-MSGV1 = I_MERRDAT-MSGV1.
 IDOC_STATUS-MSGV2 = I_MERRDAT-MSGV2.
 IDOC_STATUS-MSGV3 = I_MERRDAT-MSGV3.
 IDOC_STATUS-MSGV4 = I_MERRDAT-MSGV4.
 IDOC_STATUS-STATUS = '51'. "ERROR!
 APPEND IDOC_STATUS.
 ENDIF.
 Fill Return variables
 CLEAR RETURN_VARIABLES.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 return_variables-wf_param = c_wf_par_processed_idocs.
 RETURN_VARIABLES-WF_PARAM = 'Error_IDOCs'.
 APPEND RETURN_VARIABLES.
 WORKFLOW_RESULT = 99999.
 ENDIF.
APPEND idoc_status.
ENDLOOP.
IF NO_APPLICATION_LOG IS INITIAL.
 CALL FUNCTION 'BAL_DB_SAVE' "//br99
 EXPORTING
 I_IN_UPDATE_TASK = ' '
 I_SAVE_ALL = ' '
 I_T_LOG_HANDLE = AL_HANDLES.
 EXCEPTIONS
 LOG_NOT_FOUND = 1
 SAVE_NOT_ALLOWED = 2
 NUMBERING_ERROR = 3
 OTHERS = 4.
 CALL FUNCTION 'BAL_GLB_MEMORY_REFRESH' "//br99
 EXPORTING
 I_AUTHORIZATION =
 I_REFRESH_ALL = ' '
 I_T_LOGS_TO_BE_REFRESHED = AL_HANDLES.
 EXCEPTIONS
 NOT_AUTHORIZED = 1
 OTHERS = 2
ENDIF.
ENDFORM. " handle_error
Save, check and activate
11. Assigning the Inbound Function Module to Basic Type & Message Type
o Go to T. Code WE57
o Click on change, continue, continue and New Entries Button
o Enter the Module as IDOC_INPUT_ZBAPI_STUD_MAS
o Type as F
o Basic Type as ZBAPI_STUD_IDOC
o Message Type as ZBAPI_STUD_MAS.
o Direction as 2
o Save and back
Now Login in 810 client
12. Assigning the Inbound Function Module in ALE Table
o Go to T. Code BD51
o Click on continue, New Entries button
o Give the Inbound Function Module IDOC_INPUT_ZBAPI_STUD_MAS
o Give Input t. as 0 (zero)
o Save and back
13. Creating Process Code
o Go to T. Code WE42
o Click on Change, New Entries Button
o Give Process Code name as ZSTUD, give Description & Save
o Select Processing with ALE Services Radio button
o Select Processing by Function Module Radio button
o Click the ALE Table (arrow Icon) in Identification
o Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
o Give maximum number of repeats 0
o Save and back, back
o Select the process code from the list & click on Logical Messages Icon
o Give the Message Type as ZBAPI_STUD_MAS
o Save & Back, Save & Back, Save & Back
14. Changing the Customer Distribution model in Receiving system
o Go to T. Code BD64
o Click on change and Create model view button
o Select the model view & click on Environment -> Generate Partner Profiles
o Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o Click on Execute
o You should get a list in green color which means it executed successfully.
15. Assigning the Process Code to Message Type in Receiving System
o Go to T. Code WE20
o Expand Partner Type LS
o Select the Partner Profile STUD_S
o Double click on Message Type ZBAPI_STUD_MAS in Inbound parmtrs.
o Give the Process Code as ZSTUD
o Click on Trigger Immediately Radio button
o Save & Back
o Save & Back
16. Creating the Selection Program (Outbound Program)
 Login in client 800.
 Go to T. Code SE38
 Create a Report Program as ZSTUD_SEND with the following code
REPORT ZSTUD_SEND
 NO STANDARD PAGE HEADING.
TABLES: ZBAPI_STUD.
DATA: IT_STUD LIKE ZBAPI_STUD OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-H01.
SELECT-OPTIONS: S_ROLLNO FOR ZBAPI_STUD-ROLLNO.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN:BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-H02.
PARAMETERS: P_MESTYP LIKE EDIDC-MESTYP,
 P_RCVPRN LIKE TBDLST-LOGSYS.
SELECTION-SCREEN:END OF BLOCK B2.
SELECTION-SCREEN:END OF BLOCK B1.
START-OF-SELECTION.
PERFORM CREATE_STUDENT.
PERFORM CREATE_IDOC.
*& Form CREATE_STUDENT
 sending student
FORM CREATE_STUDENT.
SELECT * FROM ZBAPI_STUD
 INTO TABLE IT_STUD
 WHERE ROLLNO IN S_ROLLNO.
ENDFORM. " CREATE_STUDENT
*& Form CREATE_IDOC
 IDOC Creation
FORM CREATE_IDOC.
DATA : IMAS_DATA LIKE EDIDD OCCURS 10 WITH HEADER LINE,
 IMAS_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE,
 ICOM_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE.
IMAS_CON-RCVPRT = 'LS'.
IMAS_CON-RCVPRN = P_RCVPRN.
IMAS_CON-IDOCTP = 'ZBAPI_STUD_IDOC'.
IMAS_CON-MESTYP = P_MESTYP.
IMAS_CON-DIRECT = 1.
APPEND IMAS_CON.
LOOP AT IT_STUD.
IMAS_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.
IMAS_DATA-SDATA = IT_STUD.
APPEND IMAS_DATA.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 MASTER_IDOC_CONTROL = IMAS_CON
 OBJ_TYPE = ''
 CHNUM = ''
 TABLES
 COMMUNICATION_IDOC_CONTROL = ICOM_CON
 MASTER_IDOC_DATA = IMAS_DATA
 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.
ENDIF.
COMMIT WORK.
LOOP AT ICOM_CON.
WRITE :/ 'IDOC: ', ICOM_CON-DOCNUM, 'CREATED SUCCESSFULLY'.
ENDLOOP.
ENDFORM. " CREATE_IDOC
17. Transferring the student records from 800 to 810 client
 Execute Report Program ZSTUD_SEND
 Give the Range of Roll Nos to Transfer
 Give Message Type as ZBAPI_STUD_MAS
 Give Receiver Logical system as STUD_R
 Execute
 You should get the IDOC Number
 Take the IDOC Number and go to T. Code WE05 & Execute
 In Outbox you can see the IDOC Status
 Select the status record in left side window
 Double click on the Status record in right side window
 You can see the Control Record, Data Record and Status Records for that IDOC
 If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully.
Now Login in 810 client
 Go to T. Code WE05 & Execute
 You can see the status record in left side window
 If the status no is 53 and color is green, it means the IDOC is Posted to Application successfully.
 You can see the Log Information by double clicking on the status record in right side window.
 Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
 Now go to T. Code SE16
 Give the table name ZBAPI_STUD & press F7
 See the contents of the table
 The table is updated with the students records transferred from 800 client with our selection program.
Reward if useful
Thanks
Jagadeesh.G

Error to send a IDOC from ECC to SUS

Hi,
I am trying to connect to SAP SUS System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP SRM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP SUS on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have configured HTTP receiver with Addressing type HTTP Destination and configured the HTTP destination field with RFC destination(Connection Type H) created on PI. Here my source and target structures are same i.e DELVRY03. I have triggered DELVRY03 idoc from ECC and i am expecting same xml to be sent to SAP SUS but stuck up with the above mentioned error.
Someone know how fix this problem?
Tks,
Erik

HI,
As per my understanding to your scenario, You want to send one IDoc from ECC to SAP SUS system using SAP PI.
So i hope you must have configured on all the steps required to Send one IDoc to PI syste, Secondly, are you using any Standard interface in PI to send data to SAP SUS system? If yes, you need to create an HTTP Destination for that system and then you have to create XI Receiver Adapter with that HTTP destination to post incoming message to SAP SUS system.
Your error suggests you are using Plain HTTP adapter to post data to SAP SUS, which is in my understanding is incorrect.
Regards
Aashish Sinha
Edited by: Aashish Sinha on Feb 21, 2011 9:15 AM

Identifying triger point & stoping an idoc from getting generated in SD

We have 2 boxes
KLE 420 ( CRM box) & KLE 430 ( SC box)
As per original business flow
1) Sales order is generated in 420 ( order type Z001, item category ZAN1 )
2) idoc is generated and message/details is transferred to 430 ( Z002, ZAN2 )
3) in 430 the delivery & shipment is created and idoc is generated and transferred back to 420 where the invoicing happens.
As per new flow
For some selected orders, the initiation(SO) and processing needs to be completed in 430 (SC) only
When I run an order cycle, a few things I need to know is
1) how do I identify for which steps in the order cycle, an idoc is being generated
2) how can I stop this Idoc from being generated ?

Hi there,
From my experience I have seen IDOCS triggered by O/p types that are assigned to SD documents in SAP.
If that is the case, then check the sales orders what O/p types it is triggering & which O/p is triggered by EDI.
Delete the condition records for that particular O/p which is triggered by EDI. This will make the O/p not generated.
Also remove the O/p type in the determination procedure of you dont need that O/p at all. Or in the requirment routine, specify a condition like sales org or order type for which the O/p should trigger. So basing on the condition you mentioned, system will trigger the O/p accordingly.
If IDOCS are not triggered by the O/p type, then it is trigered by an external prog. In that case, specify a condition (like above) that system should not trigger the IDOCs.
Hope this helps.

Triggering IDoc from SE38

Similar Messages

Maybe you are looking for