Tracking processing log?

Hi Friends,
Its a file to file scenario.The sender SAP system writes data to the file.Based on the message no. send by sap(5 characters) how to track the processing log of that particular message processed in xi?
Thanks,
Suresh.

Hi Suresh
What exactly you want to see log for?
You can track all the steps happening at PI under SXMB_MONI
With this you can use SLG1 for application logs.
Hope this helps.
Thanks
Gaurav

Similar Messages

Processing log for customer_H fields

Dear all,
We are cusomizing the Processing Log for Service Request.
In the customizing, we can add some fields coming from the CUSTOMER_H table.
However, after adding those fields , they are not in the processing log of the transaction type in CRM7. It seems that it does not take into account the customizing. When we modify the created fields, they are not shown in the processing log history.
Would anyone had already meet this problem?
Thank you,
Regards,
Anaïs Jaussaud

Hi,
Just closing the question as I have my answer. when developpers create the fields in AET, they have a possibility to track it in the history tab.
regards,
Anaïs

ABAP Mapping - Message shown in Standard Change List Process Log

Hi
I am working with ABAP Mapping program. I had created ABAP class using ABAP workbench. Before this, in exchangeProfile..data was provided for com.sap.aii.repository.mapping.additionaltypes ==>> as " R3_ABAP|Abap-class;R3_XSLT|XSL (ABAP Engine) " and 'Saved'.
In Interface Mapping, after providing the Class Name under 'Mapping Program' and activated. After activation (Standard Change List), it is showing the following messages under 'Processing Log'.
--> Standard Change List - Process Log message
Activation of the change list canceled Check result for Interface Mapping IM_ABAP_MAPPING | http://ABAP_Mapping_SREE: Type R3_ABAP of
program ZSREETEST is invalid because it is not registered in the exchange profile . Check the values for the exchange profile parameter
IntegrationBuilder.Repository.com.sap.aii.repository.mapping.additionaltypes
--> End of Log message
Can some one please guide me in resolving the ABAP mapping issue.
Thanks in advance.
..Sree

Sree,
The log says that there is ABAP mapping included in your exchange profile. Do the things what michal have told and also check your mapping program whether working fine or not in SXI_MAPPING transaction.
You can see this weblog for reference:
/people/sameer.shadab/blog/2005/09/29/testing-abap-mapping
---Satish

Error message in processing log in VA02 in External send.

Hi,
In my smartform I am using READ_TEXT to read one text and I have checked the exceptions also in the call to function module.
CALL FUNCTION 'READ_TEXT'
EXPORTING
ID                            = 'ST'
LANGUAGE                      = ZNAST-SPRAS
NAME                          = Y_LV_NAME
OBJECT                        = 'TEXT'
TABLES
LINES                         = y_i_tline
EXCEPTIONS
ID                            = 1
LANGUAGE                      = 2
NAME                          = 3
NOT_FOUND                     = 4
OBJECT                        = 5
REFERENCE_CHECK               = 6
WRONG_ACCESS_TO_ARCHIVE       = 7
OTHERS                        = 8.
endif.
But I am not maintaining the text in SO10 and the READ_TEXT will return sy-subrc 4 .In va02 in messages tab ,I am creating output 1(print output) and 5 (external send) and save the document.when I check the processing log for both,In print output I can't see any error messages.But in external send I am getting error message that the text <my text> not found in language <my lang>.I want to know why the error message (exception thrown by READ_TEXT)comes in EXternal send in processing log and it is not coming in the processing log of print output ? .can anybody help me out ? I can't debug while saving the document since everything is handled in back groud(The smartform won't get triggered while saving).

hi
Please debug, for which u need to '/H' B4 that have a break-point in ur Driver program on SSF or the READ_TEXT Fm and SAVE in debug mode. When in DEBUG mode ,Under SETTINGS choose SYSTEM DEBUGGING and UPDATE DEBUGGING which allow you to debug and check the Error/Exception from the READ_TEXT FM ...
surya

RE: Processing Logged messages in batch mode ?

Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be
interpreted,
how can I figure out which of these log files relates to the ftexec I just
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be
interpreted,
how can I figure out which of these log files relates to the ftexec I just
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

FW: Processing Logged messages in batch mode ?

If you rename your partitions' log files before running the app and do the
renaming according to each partitions' purpose or partition number, then
after running the app, just go to the approprate log file. You can do the
renaming using system agents so that it is not a manual process.
Essentially, you know in advance where the output goes.
-Ravi
-----Original Message-----
From: J-Paul GABRIELLI [SMTP:[email protected]]
Sent: Monday, March 01, 1999 11:29 AM
To: 'Kalidindi, Ravi CWT-MSP'
Subject: RE: Processing Logged messages in batch mode ?
Sorry, I was looking for a batch way, when the partition is dead (i.E.
can't monitor it nor view it in escript)
No gui :-)
j-p
-----Message d'origine-----
De: Kalidindi, Ravi CWT-MSP [SMTP:[email protected]]
Date: lundi 1 mars 1999 17:51
A: 'Kallambella, Ajith'; 'J-Paul GABRIELLI'; 'Forte'
Objet: RE: Processing Logged messages in batch mode ?
In case of installed applications or running in distributed mode, you can
use econsole to choose the appropriate active partition and view the log
file for it. The "log file" window also displays the name of the
particular
log file. In case of installed applications, you can also rename the log
file for your partitions.
Hope that helps
-Ravi Kalidindi
Born Info Svcs Group
-----Original Message-----
From: Kallambella, Ajith [SMTP:[email protected]]
Sent: Monday, March 01, 1999 9:47 AM
To: 'J-Paul GABRIELLI'; 'Forte'
Subject: RE: Processing Logged messages in batch mode ?
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful'messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction tobe
interpreted,
how can I figure out which of these log files relates to the ftexec Ijust
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

If you rename your partitions' log files before running the app and do the
renaming according to each partitions' purpose or partition number, then
after running the app, just go to the approprate log file. You can do the
renaming using system agents so that it is not a manual process.
Essentially, you know in advance where the output goes.
-Ravi
-----Original Message-----
From: J-Paul GABRIELLI [SMTP:[email protected]]
Sent: Monday, March 01, 1999 11:29 AM
To: 'Kalidindi, Ravi CWT-MSP'
Subject: RE: Processing Logged messages in batch mode ?
Sorry, I was looking for a batch way, when the partition is dead (i.E.
can't monitor it nor view it in escript)
No gui :-)
j-p
-----Message d'origine-----
De: Kalidindi, Ravi CWT-MSP [SMTP:[email protected]]
Date: lundi 1 mars 1999 17:51
A: 'Kallambella, Ajith'; 'J-Paul GABRIELLI'; 'Forte'
Objet: RE: Processing Logged messages in batch mode ?
In case of installed applications or running in distributed mode, you can
use econsole to choose the appropriate active partition and view the log
file for it. The "log file" window also displays the name of the
particular
log file. In case of installed applications, you can also rename the log
file for your partitions.
Hope that helps
-Ravi Kalidindi
Born Info Svcs Group
-----Original Message-----
From: Kallambella, Ajith [SMTP:[email protected]]
Sent: Monday, March 01, 1999 9:47 AM
To: 'J-Paul GABRIELLI'; 'Forte'
Subject: RE: Processing Logged messages in batch mode ?
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful'messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction tobe
interpreted,
how can I figure out which of these log files relates to the ftexec Ijust
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Processing Logged messages in batch mode ?

Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under $FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be interpreted,
how can I figure out which of these log files relates to the ftexec I just got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli

The instrument "LogFile" on the active partition agent contains the name of
the log file.
At 10:47 AM 3/1/99 -0500, Kallambella, Ajith wrote:
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be
interpreted,
how can I figure out which of these log files relates to the ftexec I just
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>============================================
Don Nelson
Senior Systems Architect
Forte Software, Inc.
Denver, CO
Phone: 303-265-7709
Corporate voice mail: 510-986-3810
aka: [email protected]
============================================
"Nothing spoils fun like finding out it builds character." - Calvin
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Monitor Integration process log in BPM

Hi
I am practising the following BPM
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
and I wanted to know how to monitor integration process log in BPM.
To monitor Integration process I logged, into transaction SXMB_MONI_BPE ->Process Selection->Selected corresponding integration process (in Service Field) - and Clicked Execute as suggested in the blog
But I get the message work item doesn't exist ??
What do I need to do in this case ??
Thanks,
Kiran

SAKHARDANDE ,
Go to sxmb_moni-->Monitor for processed xml message --> In the view box there is standard and process. Select Process for checking the messages of BPM.
Else as in the weblog mentioned go to SXMB_MONI_BPE ->Process Selection->Select corresponding integration process (in Service Field) ->Execute->Select work item. Select your service which you have used in ID.
If you dont find anything then first see whether you see your message in sxmb_moni or not? If not then check your file sender communicaiton channel in adapter monitoring.
Regards,
---Satish

Message Processing Log

Hello,
I have a message processing (outbound idoc in MIRO) performed by a custom subroutine. How can I add a detail processing log so it can be seen in the output screen (MIRO->Go to->Message->Header->Process Log)?
Thank you,
Leon

Leon,
In your custom subroutine, give all your messages as information messages, as many as you want. These will be displayed as a part of the processing log of the message output.
As the program gets executed in the background, you should not see it on the screen.
I just figured out that you can NAST_PROTOCOL_UPDATE function to update the processing log with all the information messages you want.
Regards,
Ravi
note : Please close the thread, if this resolves the issues.
Message was edited by: Ravikumar Allampallam

Process Log - All Processes generates no list on 10.1.3.4

Hi,
We just upgraded to 10.1.3.4 and, unlike our previous version - 10.1.3.1 - when I select "All Processes" on the "Bpel Processes" pull down, no events are listed.
I have to select a specific BPEL process in order to see any events.
Is there any way to list the latest chronological list of events for all Processes in 10.1.3.4 (as in 10.1.3.1)?
Thank you,
AG

Our DBAs upgraded another server last night, to 10.1.3.4, MLR#8, and, still, when I go to the "Administration" - "Process Log", select "All Processes" and click Filter, nothing is shown.
Previous versions would list all activities in chronological order. This one shows a blank.
If I select a specific Bpel process, a list is generated as expected - that part is working ok.
It's the "All Processes" choice that yields no information.
Thank you for any help,
AG

Need help to get processing log for mass invoice output

Hi Experts,
I have one requirement,
My customer will send invoices to their customers in bulk on monthly basis. The customers will receive the invoices through emails, fax or printout. Now the issue is when they send the output to the customers there might be some failures in delivery because of some reason to some customers. I want to capture all the invoices, customers, medium and error text and want to display as a report.
We can see the processing log for a single invoice in VBFA transaction but I want to display one consolidated list where the user can see all the error log records at one place.
I know some tables where we can see some data in NAST, NACH but I would be greatful to you if you provide some more information about this.
Please provide whatever info you have.
Regards,
Dileep.

Hi Study abap,
go through this code and use the HTEXT fm accordingly to ur requirement. This is just a sample kind of thing which will help u to write s-kunnr in htext.
SELECT-OPTIONS: S_MATNR FOR PBIM-MATNR,
S_WERKS FOR PBIM-WERKS.
DATA: BEGIN OF HTEXT.
INCLUDE STRUCTURE THEAD.
DATA: END OF HTEXT.
DATA: BEGIN OF LTEXT OCCURS 50.
INCLUDE STRUCTURE TLINE.
DATA: END OF LTEXT.
DATA: BEGIN OF DTEXT OCCURS 50.
DATA: MATNR LIKE PBIM-MATNR.
INCLUDE STRUCTURE TLINE.
DATA: END OF DTEXT.
DATA: TNAME LIKE THEAD-TDNAME.
SELECT * FROM PBIM WHERE WERKS IN S_WERKS.
MOVE PBIM-BDZEI TO TNAME.
CALL FUNCTION 'READ_TEXT'
EXPORTING
CLIENT = SY-MANDT
ID = 'PB'
LANGUAGE = 'E'
NAME = TNAME
OBJECT = 'PBPT'
ARCHIVE_HANDLE = 0
IMPORTING
HEADER = HTEXT
TABLES
LINES = LTEXT
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
NOT_FOUND = 4
OBJECT = 5
REFERENCE_CHECK = 6
WRONG_ACCESS_TO_ARCHIVE = 7
OTHERS = 8.
LOOP AT LTEXT.
IF LTEXT-TDLINE NE ''.
MOVE LTEXT-TDLINE TO DTEXT-TDLINE.
MOVE PBIM-MATNR TO DTEXT-MATNR.
APPEND DTEXT.
ENDIF.
ENDLOOP.
ENDSELECT.
LOOP AT DTEXT.
WRITE:/ DTEXT-MATNR, DTEXT-TDLINE.
ENDLOOP.
Kindly reward fi found helpful.
cheers,
Hema.

Tracking change log by workstation ID along with username

Hi All users,
I am using SAP business one 8.8 and want to track changes in the system in such a way that along with user name I want to know, from which workstation (or PC) the user has made changes or created any document? Every PC has its unique IP or ID, can I see this in change log in any way? that from which workstation or client PC, the user has made changes?
Any help is highly appreciated.
Thanks in advance,
Farhan Sufi

Dear Gordon,
Thanks for your reply, Actually I need only workstation ID along with user name when tracking transaction log from the tools option "change log".
I am calling it workstation ID, but you can tell me about any thing from which I can track, from which client or PC the user made any transaction. Whether It gives me computer IP or computer name or any identity of PC by which I can know which PC (among server and clients) is used by user to make any transaction.
Any help is appreciated
Thanks,
Farhan

No processing log generated from the output type for the IDOC

Dear experts,
the output type which is triggered with a transmission medium Special Function has not generated any IDOC.
The question is what is the role of a Special function and EDI transmission.
In some cases the system has generated an IDOC and some cases not. The output is pickedup automatically, but
does not always trigger an IDOC, Thats is the issue I am facing.
Therefore in cases where there was no IDOC created there is no processing log generated.
KIndly help.

The status is green, and when I try to show the IDOC it doesnt show and no processing log.
The same output is processed for a delivery and it creates a IDOC but sometimes it doesnt.

Processing log not getting updated for send immediatly

Hi,
I have a custom output type and a Custom function module for issueing the output for delivery, my prob is that it processing log is getting updated for the send in batch and other options but it is not getting updated for the SEND IMMEDIATLY, I am using the same FM for the Output issue I am checking if they have selected output type as 4 if yes, I am calling a FM in perform by saying
PERFORM xxxxxxxx ON COMMIT
and in the perform I am calling a FM
CALL FUNCTION xxxxxxxxx in BACKGROUND TASK AS A SEPARATE TASK,
the functioanlity of issueing the output is working but the Processing log is not getting updated.
What might be the problem ? it is getting updated for Send in batch but not for except 4.

I am updating Log using this form
at every step I am collecting the messages and passing them to this form.
FORM update_nast_log USING   p_msgid
                              p_msgnr
                              p_msgty
                              p_msgv1
                              p_msgv2
                              p_msgv3
                              p_msgv4.
* Local data declaration
DATA: lv_msgid LIKE sy-msgid,
        lv_msgnr LIKE sy-msgno,
        lv_msgty LIKE sy-msgty,
        lv_msgv1 LIKE sy-msgv1,
        lv_msgv2 LIKE sy-msgv2,
        lv_msgv3 LIKE sy-msgv3,
        lv_msgv4 LIKE sy-msgv4.
* clear all the local variables
CLEAR:lv_msgid,
        lv_msgnr,
        lv_msgty,
        lv_msgv1,
        lv_msgv2,
        lv_msgv3,
        lv_msgv4.
* move message ID,number,msg type and the messsages
*     to local variables
MOVE: p_msgid TO lv_msgid,
        p_msgnr TO lv_msgnr,
        p_msgty TO lv_msgty,
        p_msgv1 TO lv_msgv1,
        p_msgv2 TO lv_msgv2,
        p_msgv3 TO lv_msgv3,
        p_msgv4 TO lv_msgv4.
* Update nast table using nast protocol update
CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
    EXPORTING
      msg_arbgb = lv_msgid
      msg_nr    = lv_msgnr
      msg_ty    = lv_msgty
      msg_v1    = lv_msgv1
      msg_v2    = lv_msgv2
      msg_v3    = lv_msgv3
      msg_v4    = lv_msgv4.
ENDFORM.                    " UPDATE_NAST_LOG

Processing log output for Purchase order

Dear All,
Iam getting some problem when iam creating an IDOC and checking in the Processing log for IDOC number.
Actually i had created one custom idoc for Purchase order since my client need only some field and in one line for header and line item, I had done it and i can see it in sdata of EDIDD structure. When i create a Purchase order and save it an idoc number is posting and I can see this file in my physical directory indeed.
Now when iam going into change mode of PO ME22n to see the Processing LOG, It is not showing the IDOC Number in Purchase order output processing log popup.

The processing log will only show output based standard output control (Table NAST).
How is your IDoc being created. Via a user exit, BADI. If so then they will not appear on the processing log.
It is being created as a custom IDOC for which i had written a Z function module and given that in PO processing code which is ME10. When iam checking the standard IDOC for PO it is generating the IDOC in processing log as well.
Iam just placing my code just have a look at it and suggest if any thing needs to be done.
FUNCTION Z_IDOC_OUTPUT_ORDERS.
""Local Interface:
*" IMPORTING
*"     VALUE(OBJECT) LIKE NAST STRUCTURE NAST
*"     VALUE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*"     VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*"      INT_EDIDD STRUCTURE EDIDD
*" EXCEPTIONS
*"      ERROR_MESSAGE_RECEIVED
*"      DATA_NOT_RELEVANT_FOR_SENDING
DATA: xdruvo.                          "Druckvorgang
DATA: neu VALUE '1',                  "Neudruck
      h_kappl LIKE nast-kappl,         "Hilfsfeld Applikation
      h_parvw LIKE ekpa-parvw,         "Hilfsfeld Partnerrolle
      h_ebeln LIKE ekko-ebeln.         "Hilfsfeld Belegnummer
CLEAR control_record_out.
   xdruvo = neu.
h_kappl = object-kappl.
h_ebeln = object-objky.
h_parvw = object-parvw.
DATA:
       LT_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
         L_EDIDC LIKE EDIDC,
         L_SEND_FLAG,
         W_SDATA LIKE EDIDD-SDATA.
DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA: C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'ZORDER'.
*- Call function module to determine if message is to be distributed
OBJECT_TYPE = 'BUS2012'.
MOVE control_record_in TO control_record_out.
CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'
    EXPORTING
      MESSAGE_TYPE           = C_MESSAGE_TYPE
    IMPORTING
      IDOC_MUST_BE_SENT      = L_SEND_FLAG.
   EXCEPTIONS
     OWN_SYSTEM_NOT_DEFINED = 1
     OTHERS                 = 2.
DATA : BEGIN OF EKKO_tAB OCCURS 0,
EBELN LIKE EKKO-EBELN,
F1 TYPE C VALUE ',',
BUKRS LIKE EKKO-BUKRS,
F2 TYPE C VALUE ',',
BSART LIKE EKKO-BSART,
F3 TYPE C VALUE ',',
LIFNR LIKE EKKO-LIFNR,
F4 TYPE C VALUE ',',
WAERS LIKE EKKO-WAERS,
F5 TYPE C VALUE ',',
BEDAT LIKE EKKO-BEDAT,
F6 TYPE C VALUE ',',
WERKS LIKE EKPO-WERKS,
F7 TYPE C VALUE ',',
PLIFZ LIKE EKPO-PLIFZ,
F8 TYPE C VALUE ',',
EBELP LIKE EKPO-EBELP,
F9 TYPE C VALUE ',',
MATNR LIKE EKPO-MATNR,
F10 TYPE C VALUE ',',
MENGE LIKE EKPO-MENGE,
F11 TYPE C VALUE ',',
MEINS LIKE EKPO-MEINS,
F12 TYPE C VALUE ',',
END OF EKKO_TAB.
DATA SDATA1 LIKE EKKO_tAB OCCURS 0 WITH HEADER LINE.
DATA EBELN LIKE EKKO-EBELN.
WRITE OBJECT-OBJKY TO EBELN.
SELECT T1EBELN T1BUKRS BSART LIFNR WAERS BEDAT WERKS PLIFZ EBELP MATNR MENGE MEINS
FROM EKKO AS T1
INNER JOIN EKPO AS T2 ON T2EBELN = t1EBELN
INTO CORRESPONDING FIELDS OF TABLE EKKO_tAB
WHERE
*T1~KAPPL = 'EF' AND
T1~EBELN = EBELN.
*T1~KSCHL = 'YEDI' .
DATA SDATA LIKE EDIDD-SDATA.
DATA NDATE LIKE SY-DATUM.
DATA NMENGE(17) TYPE C.
LOOP AT EKKO_tAB.
    WRITE EKKO_TAB-MENGE TO NMENGE.
    NDATE = EKKO_tAB-BEDAT + EKKO_tAB-PLIFZ.
    CONCATENATE EKKO_tAB-EBELP ',' EKKO_tAB-BUKRS ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-LIFNR ',' EKKO_tAB-BEDAT ','
    NDATE ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-EBELN ', 0,' EKKO_tAB-MATNR ','
    NMENGE ',' EKKO_tAB-MEINS ',' EKKO_tAB-WERKS INTO SDATA.
    MOVE SDATA TO: W_SDATA, T_EDIDD-SDATA.
    MOVE 'ZORDERS' TO T_EDIDD-SEGNAM.
    APPEND T_EDIDD.
ENDLOOP.
*call function 'L_IDOC_SEGMENT_CREATE'
    exporting
         i_segnam = 'ZORDERS'
         i_sdata = w_sdata
    exceptions
         others   = 1.
*LT_EDIDC
call function 'L_IDOC_SEND'
     tables
          t_comm_idoc           = LT_EDIDC
     exceptions
          error_distribute_idoc = 1
          others                = 2.
*DATA T_BDI_MODEL LIKE BDI_MODEL.
WRITE OBJECT-OBJKY TO T_BDI_MODEL.
READ TABLE T_BDI_MODEL INDEX 1.      " maximum 1 recipient
L_EDIDC-DIRECT = 1.
L_EDIDC-DOCNUM = DOCNUM. "***
L_EDIDC-RCVPRN = 'HCM_00_785'.
L_EDIDC-RCVPOR = 'MM_PO_FILO'.
MOVE 'ZORDER'   TO L_EDIDC-MESTYP.
MOVE 'ZPURIDOC' TO L_EDIDC-IDOCTP.
MOVE 'LS'      TO L_EDIDC-RCVPRT.
MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.
*MOVE-CORRESPONDING L_EDIDC TO W_EDIDC.
*- Distribute the iDoc
BREAK-POINT.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' "IN UPDATE TASK
    EXPORTING
      MASTER_IDOC_CONTROL            = L_EDIDC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = LT_EDIDC
      MASTER_IDOC_DATA               = T_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 01
      ERROR_WRITING_IDOC_STATUS      = 02
      ERROR_IN_IDOC_DATA             = 03
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE LT_EDIDC INDEX 1.
control_record_out-direct = '1'.
CONTROL_RECORD_OUT-DOCNUM = DOCNUM. " ***
control_record_out-serial = sy-datum.
control_record_out-serial+8 = sy-uzeit.
control_record_out-mestyp = LT_EDIDC-mestyp.
control_record_out-idoctp = LT_EDIDC-idoctp.
control_record_out-SNDPRN = 'HCM_00_786'.
MOVE 'MM_PO_FILO' TO control_record_out-RCVPOR.
MOVE 'LI'      TO control_record_out-SNDPRT.
MOVE 'SAPQIS' TO control_record_out-SNDPOR.
ENDFUNCTION.

Tracking processing log?

Similar Messages

Maybe you are looking for