How to verify the message id for call transaction ?

Hi all,
After calling transaction, I collect the message into a message table msgtab. There is an entry in msgtab with message type (MSGTYP) and message id (MSGID).
How to know that the message type and message id is correct / relevant to my transaction?

Hi macy,
1. How to know that the message type and message id is correct / relevant to my transaction?
I don't think thats requried,
bcos,
these message are ISSUED from the
TRANSACTION itself.
The message id, which is used in the transaction,
(it can be more than one message id used in the transaction)
, the same is collected in the table.
regards,
amit m.

Similar Messages

How to create a background job for call transaction

hi gurus
can any one suggest me
how to create the background job for call transaction.
thank you
regards
kals.

Hi,
Refer
https://forums.sdn.sap.com/click.jspa?searchID=10926107&messageID=889652
Regards
Kiran Sure

How look the flat file for CALL Transaction

Hi ABAPERS
i am new for BDC i want to know how the flat file format for call transaction execution.
if any one have sample flat file data for any transaction please send me.

Hi,
The file format differ for different transaction. Basically you can have the field in any order. It matters how you upload into SAP. Use the function module GUI_UPLOAD to upload the flat file.
Please see this sites for more info.
http://www.sap-img.com/abap/learning-bdc-programming.htm
Help with BDCs and flat files.....
Cheers
Vinod
Message was edited by: Vinod C

How to find the BTE event for FBCJ transaction code

Hi All,
i need to find the BTE event for Finance related transaction codes.i checked in the SWEL transaction code, didnt find any event triggered and the standard BADI doesnt suite my requirement.The transaction code which i tried is FBCJ.can anyone help me how to find the BTE event for the above mentioned transaction.
Thanks in Advance,
lokesh kumar.K

Hello Lokesh,
The following is one of the process of finding a BTE and implementing it.
(1)Goto transction FIBF .Execute it with Attribute type = 'A'. Then in the menubar Environment->Info System (P/S )
Go through the list of BTE's available with the description available beside.
(2)Select the BTE you want to implement.
(3)Press button Sample function module
(4)This brings you to SE37 - Copy the sample function module to a Z-function module (First create a new function group for the function module) . Note: The name of the Z-functionmodule is not important
(5)Edit the code in the new function module
(6)Go back to transaction FIBF - Menu Settings->Products -> Of a customer and create a new product whicj identifies the new product . Remember to mark the Active field.
(7)Go back to FIBF menu Settings->P/S function modules->of a customer - Create an entry that links the BTE and Product with the new function module
Hope this will help.
Regards,
Samson

How to show the message text for constraint violations

Hi all,
In a batch procedure a primary key is violated (ORA-00001). For the primary key, a message is recorded in the TAPI and the message table.
How to show the enduser a proper message text instead of the ORA-00001.
We are using Designer 6 with Headstart 2.1.2.
Thanks in advance,
Joep

Joep,
If you try to insert the record by calling the ins procedure of the Table API, you will see that it will result in an ORA-20998 message, which means that the error message details reside in the CG$ERRORS plsql message table. These messages can be extracted e.g. with the messages.sql script, shipped with headstart.
If you do not want to rewrite your direct DML (insert into [table name] ...) in the complexer calls to the TAPI services, you might want to user VAPI's for it. In fact, this is one of the major advantages of using VAPI's.
The CDM guidelines volume, chapter 6 states that:
The front end no longer needs to trap declarative constraint
errors (Primary Key, Unique Key, Not Null and Check
Constraint violations) and replace them with a user-friendly
error. The View API issues DML statements through the TAPI
and the TAPI traps all declarative constraint errors, and puts
user-friendly message on the stack, in the preferred language of
the user! Fore more information, see the section, Completeness
of Rule Violations Reported in Front End, in this chapter.
So the only thing you need to do is generate VAPI's, and trap the ORA-20998 message (qms$errors.qms$exception) in an exception handler, where you retrieve the user friendly messages from the message stack!!
Regards, Marc

How to find the message type for application

Hi Guys,
while postnig the data through idocs,we use message types
the issue is how can we find the massage type for application?
plzz help

You can find these in transaction WE82.
You can find in WE57, this basis type, which fm is attached (BAPI_IDOC_INPUT1).
Then check out transactions WE41 and WE42.
You can use the table EDIMSG, in SE16 to list all the msg types making use of the same IDoc.
or
If you want to get all the message types, you can use WE81.
If you want to see which message types are attched to a particular Idoc type, use WE82
check it in BD60 and WE57..

How to configure the message control for DESADV

dear friends .
my requiremnet is i have to write the outbound for DESADV message type for extended IDOC : ZDESADV01.
pls tell me solution briefly

Hi...
How do we use IDoc to create Outbound delivery document using the transaction VL01N.
Do following steps..
Go to NACE and select V2 and click output type from menu.
Give following value.
Condition component Value
Access sequence 0005 (sales organization/customer)
Condition 0 (no condition)
Exclusive select
Output type LAVA (shipping notification outbound)
Procedure V10000 (shipping output)
Application V2 (shipping)
Processing subroutine Program RSNASTED,
form routine EDI-PROCESSING
General data Select Condition access and Multiple sending of output, otherwise
leave the fields blank
Time e.g. 4 (immediately, IDocs are generated immediately after
posting)
Transmission medium 6
Partner function WE
Language DE (German)
You must maintain following values for outbound partner profile.
Output category : Desadv
Partner type : Ku
Partner function : WE
Port : Subsystem
Output mode: Collect idoc
Basic type : Delvry01
Packet size: 1
Application: V2
Output type : LAVA
Process code: DELV.
You can post the delivery by selecting Shipping, Delivery>Sales and Distribution >Logistics
-->Create (transaction VL01N). Output control is used to find the condition record and the shipping
notification is sent to the customer via EDI (IDoc Interface). The shipping time in the condition
record determines when the corresponding outbound IDoc is generated.
Reward if Helpful.

How to resolve the error in bdc call transaction in ALV report

Dear Experts, i am executing the alv report program and in alv report program one bdc is there..
after executing output is showing in alv format but one button is there (update master)..when i am clicking update button the bdc is run but is not updated in the material master..after executing my bdc is not updated in mm02.
how to resove it?
CALL TRANSACTION 'MM02' USING BDCDATA MODE MODE
UPDATE 'S'
MESSAGES INTO MESSTAB.

Hi Kaustav,
Looking at the code you attached, it appears to me that your BDC (Form USER_COMMAND) is not executed at all as you haven't passed the 'USER_COMMAND' in FM REUSE_ALV_GRID_DISPLAY for ALV display.
You must pass the importing parameter I_CALLBACK_USER_COMMAND of this FM as 'USER_COMMAND', only then this form will be executed and your BDC will run.
Thereafter, in case your BDC update fails, you can put a break-point in the form (at CALL TRANSACTION statement) and analyze the message table MESSTAB.
Hope it helps.
Regards,
Sapeksh

XI: How to update the Message Status (shown by transaction SXMB_MONI )

Hi
My question might be stupid, but I need you help.
I would like to know how can I update the message status what we see while using trasaction SXMB_MONI . The Scenrio is, I have a Custom Interface program build on the Abap Proxy interface method called EXECUTE_ASYNCHRONOUS.
If I am not wrong, transaction SXMB_MONI is on the XI system and also on the SAP Application system. ( But I am not sure in what way the same transaction differ in two systems )
My issue is, when I receive the xml data into a structure in abap proxy, I am doing some validation on the received message data. If I found some error in the data , then I need to update the Message status of the SXMB_MONI to ERROR flag. How to implement this ? I have not done one before. And I am not sure, if any exception like error message is raised, will it stop the proxy from processing further and update the Message Status and this can be viewed using SXMP_MONI in the SAP application system to be ERROR flag?
Or is there a BAPI or function module to handle this ?
Appreciate your help
David

Hi
I am not sure If I had understood you reply. But Would need your help to have a bit more insight to your answer. I am not completely into XI , but I am from ABAP side.
At the R/3 side , Abap Proxy object geneted has the INTERFACE and its associated METHOD, in which I am building my own abap code to do any validation on incomming data. But If I want to Raise a Exception, I understand that this Expection has to be first defined .
But do I have to define a new Z Expection class or can I just add a exception in the Proxy -Interface-method.
I have not understood this process.
All I need to do is, if I find any incomming data error , during my validation at the R/3 side, I need to stop the METHOD processing ( by any means ) and Update the Message Status flag show in SXMB_MONI to Error .
What is the trigger that i can implement in myown code that will update the Message status to Error , from R/3 perspective of using SXMB_MONI.
Thanks
David

Pls tell me how to check the errors in BDC CALL TRANSACTION

lemme know

HI ,
check for the bold part..
REPORT ZCONCUR_UPLOAD_TO_SAP NO STANDARD PAGE HEADING
 LINE-SIZE 170
 LINE-COUNT 58
 MESSAGE-ID ZM.
 Internal Table *
*-Internal table for the Header input data from the Comma Delimited file
DATA: BEGIN OF IT_DATA_HEADER OCCURS 0,
 ID TYPE C, "Identifier
 BUKRS(6), "Company Code
 WAERS(7), "Currency
 NEWKO(12), "Vendor
 XBLNR(16), "First Name
 XBLNR1(16), "Last Name
 BLDAT(12), "Document/Posting date
 PK(15), "Reference
 WRBTR(15), "Amount
 BKTXT(27), "Doc.header text
 BKTXT1(27), "Item text
 SELNO(8), "Serial No
 END OF IT_DATA_HEADER.
*-Internal table for the item input data from the Comma Delimited file
DATA: BEGIN OF IT_DATA_ITEM OCCURS 0,
 ID TYPE C, "Identifier
 NEWKO(19), "Vendor
 BUKRS(6), "Company Code
 KOSTL(12), "Cost center
 WRBTR(15), "Amount
 SGTXT(50), "Text
 SELNO(8), "Serial No Header
 SELNO1(8), "Serial No item
 END OF IT_DATA_ITEM .
*-Internal table for the Header input data from the Comma Delimited file
*-Removing " " From Comma Delimited file
DATA: BEGIN OF IT_FINAL_HEADER OCCURS 0,
 ID TYPE C, "Identifier
 BUKRS LIKE BKPF-BUKRS, "Company Code
 WAERS LIKE BKPF-WAERS, "Currency
 NEWKO TYPE RF05A-NEWKO, "Vendor
 XBLNR LIKE BKPF-XBLNR,
 XBLNR1 LIKE BKPF-XBLNR,
 BLDAT(10), " LIKE BKPF-BLDAT, "Date
 PK(15), "Reference
 WRBTR(15), "Amount
 BKTXT LIKE BKPF-BKTXT, "Doc.header text
 BKTXT1 LIKE BKPF-BKTXT, "Item text
 SELNO TYPE I, "Serial No
 FLAG TYPE C,
 END OF IT_FINAL_HEADER.
*-Internal table for the Item input data from the Comma Delimited file
*-Removing " " From Comma Delimited file
DATA: BEGIN OF IT_FINAL_ITEM OCCURS 0,
 ID TYPE C, "Identifier
 NEWKO TYPE RF05A-NEWKO, "Account
 BUKRS LIKE BKPF-BUKRS, "Company Code
 KOSTL LIKE BSEG-KOSTL, "Cost Center
 WRBTR(15), "Amount
 SGTXT LIKE BSEG-SGTXT, "Text
 SELNO TYPE I, "Serial No
 SELNO1 TYPE I, "Serial No
 END OF IT_FINAL_ITEM.
**-Internal table for the input data from the file
DATA : BEGIN OF P_DOWNLOAD OCCURS 0,
 V_FILEREC(1000) TYPE C,
 END OF P_DOWNLOAD.
*--- Internal Table for Success messages
DATA : BEGIN OF I_SUCC OCCURS 0,
 HEADER(50),
 MSG(100), "SUCCESS message
 END OF I_SUCC.
*--- Internal Table for error messages
DATA : BEGIN OF I_ERROR_LOG OCCURS 0,
 HEADER(50),
 MSG(100), "Error message
 END OF I_ERROR_LOG.
*--- Internal table for getting the BDC data
DATA : BEGIN OF IT_BDCDATA OCCURS 0.
 INCLUDE STRUCTURE BDCDATA. " Table to hold BDC data
DATA : END OF IT_BDCDATA.
*--- Internal table for reading the messages of call transaction
DATA : BEGIN OF IT_MESSAGE_TAB OCCURS 0.
 INCLUDE STRUCTURE BDCMSGCOLL. "Table to hold messages
DATA : END OF IT_MESSAGE_TAB.
 DATA DECLARATIONS *
DATA:
 V_ERROR_COUNTER TYPE I, " error records counter
 V_MSG(100), " used for Error message
 V_LINES TYPE I, " used for format message
 V_HEAD LIKE SY-CPROG, " Heading for report
 XMODE VALUE 'N', " EXECUTION MODE
 V_SUCCESS_COUNTER TYPE I, " Success records counter
 V_UNAME LIKE APQI-USERID, " User Name
 V_TOTAL TYPE I. " Total records uploaded
DATA : V_SELNO TYPE I.
DATA : V_CHECK TYPE I.
DATA : V_HEADER(50) TYPE C. "Header Information
DATA : V_SUCC_MSG LIKE BDCMSGCOLL-MSGV1."Success Message
DATA : V_ZERO(4) VALUE '0.00'. "Checking Zero
DATA : V_CHECK_ZERO LIKE BSEG-WRBTR. "Checking Zero
DATA : V_CHECK_ZERO1 LIKE BSEG-WRBTR. "Checking Zero
DATA : V_SYSTEMDATE LIKE BKPF-BUDAT.
DATA : V_VALUE TYPE I.
DATA : V_VALUE1 TYPE I.
DATA : V_VALUE2 TYPE I.
Flags
DATA:
 F_BDC_OPEN, " BDC session open check.
 F_CONTINUE_PROCESSING. " To continue further processing
 CONSTANTS *
CONSTANTS:
 C_SESSION_NAME LIKE APQI-GROUPID VALUE 'F-43', "Session
 C_X VALUE 'X'. " Used for falgs
 SELECTION SCREEN *
*--- Selection Screen with Block and title
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-038.
PARAMETER: P_FNAME LIKE RLGRAP-FILENAME DEFAULT
 'C:\Concur.txt'.
SELECTION-SCREEN END OF BLOCK B1.
AT SELECTION SCREEN ON VALUE-REQUEST
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FNAME.
CALL FUNCTION 'F4_FILENAME'
 IMPORTING
 FILE_NAME = P_FNAME
 EXCEPTIONS
 OTHERS = 1.
IF SY-SUBRC <> 0.
 MESSAGE E999 WITH 'Error in opening a file'(009).
ENDIF.
 Top-of-page *
TOP-OF-PAGE .
*---perform to display the standard header
PERFORM STANDARD_HEADER.
--START OF SELECTION--
START-OF-SELECTION.
Upload data
PERFORM UPLOAD_DATA.
move data to bdcdata internal table
PERFORM MOVE_DATA_F43.
*--- Posting the valid data to F-43
IF F_BDC_OPEN = C_X.
*---perform to close bdc group
 PERFORM CLOSE_GROUP.
ENDIF.
 END OF SELECTION *
END-OF-SELECTION.
CHECK F_CONTINUE_PROCESSING IS INITIAL.
PERFORM DISPLAY_REPORT.
*& Form MESSAGE_FORMAT
 MESSAGE FORMAT
FORM MESSAGE_FORMAT.
CLEAR V_MSG.
CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = IT_MESSAGE_TAB-MSGID
 LANG = 'EN'
 NO = IT_MESSAGE_TAB-MSGNR
 V1 = IT_MESSAGE_TAB-MSGV1
 V2 = IT_MESSAGE_TAB-MSGV2
 V3 = IT_MESSAGE_TAB-MSGV3
 V4 = IT_MESSAGE_TAB-MSGV4
 IMPORTING
 MSG = V_MSG
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
 V_MSG = SPACE.
ENDIF.
ENDFORM. " MESSAGE_FORMAT
*& Form F4_HELP
FORM F4_HELP.
CALL FUNCTION 'WS_FILENAME_GET'
 EXPORTING
 DEF_FILENAME = ' '
 DEF_PATH = 'C:\'
 MODE = 'O'
 TITLE = TEXT-025 "'Upload File'
 IMPORTING
 FILENAME = P_FNAME
 EXCEPTIONS
 SELECTION_CANCEL = 3
 SELECTION_ERROR = 4.
CASE SY-SUBRC.
 WHEN 3.
 MESSAGE I000 WITH TEXT-007. " Selection Cancel.
 WHEN 4.
 MESSAGE I000 WITH TEXT-008. " Selection Error.
ENDCASE.
ENDFORM. " F4_HELP
*& Form STANDARD_HEADER
 STANDARD_HEADER
FORM STANDARD_HEADER.
FORMAT COLOR COL_HEADING INTENSIFIED OFF.
CASE V_HEAD.
 WHEN 'Summary Report'(001).
 WHEN 'SUCC_REPORT'.
**---To display the field headings for Success report.
 ULINE (154).
 WRITE : /001 SY-VLINE,
 002 'Header Details '(011),
 052 SY-VLINE,
 053 'Document Number'(036),
 154 SY-VLINE.
 ULINE (154).
 WHEN 'Error Report'.
**---To display the field headings for error report.
 ULINE (154).
 WRITE : /001 SY-VLINE,
 002 'Header Details '(011),
 052 SY-VLINE,
 053 'Error Message/Text'(035),
 154 SY-VLINE.
 ULINE (154).
ENDCASE.
ENDFORM. " STANDARD_HEADER
*& Form DISPLAY_REPORT
 Display Report Details
FORM DISPLAY_REPORT.
PERFORM SUMMARY_REPORT.
PERFORM SUCC_REPORT.
PERFORM ERROR_REPORT.
ENDFORM. " DISPLAY_REPORT
*& Form SUMMARY_REPORT
 Success & Error Count Number
FORM SUMMARY_REPORT.
WRITE : /030 SY-TITLE.
SKIP 1.
WRITE : /005 'Program Name : '(032),
 024 SY-REPID,
 080 'Date :'(033),
 088 SY-DATUM.
SKIP 1.
V_HEAD = 'Summary Report'(001).
ULINE (132).
WRITE : /1 SY-VLINE,
 5 'No. of Records read from the Data file'(014),
 45 ':', V_TOTAL LEFT-JUSTIFIED,
 132 SY-VLINE,
 /1 SY-VLINE,
 5 'No. of Records successfully posted'(015),
 45 ':', V_SUCCESS_COUNTER LEFT-JUSTIFIED,
 132 SY-VLINE,
 /1 SY-VLINE,
 5 'No. of Records Failed'(023),
 45 ':'(031), V_ERROR_COUNTER LEFT-JUSTIFIED,
 132 SY-VLINE.
IF NOT F_BDC_OPEN IS INITIAL.
 WRITE: /1 SY-VLINE,
 5 'Session Name'(022),
 45 ':'(031), C_SESSION_NAME LEFT-JUSTIFIED,
 132 SY-VLINE.
ENDIF.
ULINE (132).
IF NOT F_BDC_OPEN IS INITIAL.
 WRITE: /1 SY-VLINE,
 5 'Session Name'(022),
 45 ':'(031), C_SESSION_NAME LEFT-JUSTIFIED,
 132 SY-VLINE.
ENDIF.
ULINE (132).
ENDFORM. " SUMMARY_REPORT
*& Form ERROR_REPORT
 Error Report
FORM ERROR_REPORT.
IF NOT I_ERROR_LOG[] IS INITIAL.
 SORT I_ERROR_LOG. " by tcode.
 V_HEAD = 'Error Report'(013).
 NEW-PAGE.
 LOOP AT I_ERROR_LOG.
 WRITE: /001 SY-VLINE,
 002 I_ERROR_LOG-HEADER,
 052 SY-VLINE,
 053 I_ERROR_LOG-MSG,
 154 SY-VLINE.
 ULINE (154).
 ENDLOOP.
ENDIF.
ENDFORM. " ERROR_REPORT
*& Form ERROR_REPORT
 Success Report
FORM SUCC_REPORT.
IF NOT I_SUCC[] IS INITIAL.
 SORT I_SUCC. " by tcode.
 V_HEAD = 'SUCC_REPORT'(034).
 NEW-PAGE.
 LOOP AT I_SUCC.
 WRITE: /001 SY-VLINE,
 002 I_SUCC-HEADER,
 052 SY-VLINE,
 053 I_SUCC-MSG,
 154 SY-VLINE.
 ULINE (154).
 ENDLOOP.
ENDIF.
ENDFORM. " SUCC_REPORT
*& Form OPEN_SESSION
FORM OPEN_SESSION.
DATA : V_DATE LIKE SY-DATUM. " For Hold Date.
V_DATE = SY-DATUM - 1. " Hold date
V_UNAME = SY-UNAME. " User name
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = C_SESSION_NAME
 HOLDDATE = V_DATE
 KEEP = 'X'
 USER = V_UNAME
 EXCEPTIONS
 CLIENT_INVALID = 1
 DESTINATION_INVALID = 2
 GROUP_INVALID = 3
 GROUP_IS_LOCKED = 4
 HOLDDATE_INVALID = 5
 INTERNAL_ERROR = 6
 QUEUE_ERROR = 7
 RUNNING = 8
 SYSTEM_LOCK_ERROR = 9
 USER_INVALID = 10
 OTHERS = 11.
IF SY-SUBRC <> 0.
 MESSAGE I000 WITH 'Session can not be opened'(019).
 STOP.
ENDIF.
F_BDC_OPEN = 'X'.
ENDFORM. " OPEN_SESSION
*& Form BDC_INSERT
FORM BDC_INSERT USING P_TCODE TYPE ANY.
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = P_TCODE
 TABLES
 DYNPROTAB = IT_BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 MESSAGE I000 WITH 'Unable to insert, Error record'(037).
 STOP.
ENDIF.
ENDFORM. " BDC_INSERT
*& Form CLOSE_GROUP
FORM CLOSE_GROUP.
CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 NOT_OPEN = 1
 QUEUE_ERROR = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 MESSAGE I000 WITH 'Session can not be closed'(021).
 STOP.
ENDIF.
ENDFORM. " CLOSE_GROUP
*& Form UPLOAD_DATA
 Upload Data From the text file
FORM UPLOAD_DATA.
CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 FILENAME = P_FNAME
 FILETYPE = 'DAT'
 TABLES
 DATA_TAB = P_DOWNLOAD
 EXCEPTIONS
 CONVERSION_ERROR = 1
 FILE_OPEN_ERROR = 2
 FILE_READ_ERROR = 3
 INVALID_TYPE = 4
 NO_BATCH = 5
 UNKNOWN_ERROR = 6
 INVALID_TABLE_WIDTH = 7
 GUI_REFUSE_FILETRANSFER = 8
 OTHERS = 10.
IF SY-SUBRC NE 0.
 MESSAGE E000 WITH 'File does not Exist'(003).
ELSEIF P_DOWNLOAD[] IS INITIAL.
 MESSAGE E000 WITH 'Input file is empty'(004).
ENDIF.
DATA: V_INDEX LIKE SY-TABIX.
IF NOT P_DOWNLOAD[] IS INITIAL.
 LOOP AT P_DOWNLOAD.
 V_INDEX = SY-TABIX.
*Removing double quotes
 DO.
 REPLACE '"' WITH '' INTO P_DOWNLOAD.
 IF SY-SUBRC NE 0.
 EXIT.
 ENDIF.
 ENDDO.
 MODIFY P_DOWNLOAD INDEX V_INDEX.
 CONDENSE P_DOWNLOAD.
 IF P_DOWNLOAD(1) = '1'.
*Finding the header information, creating key field
 V_SELNO = SY-TABIX.
 ENDIF.
WE ARE NOT HAVING KEY FIELD IN HEADER/ITEM IN THE FILE.
SO WE ARE CREATING MANUAL KEY FIELD IN INTERNAL TABLE (SELNO).
 IF P_DOWNLOAD(1) = '1'.
Moving header information into IT_DATA_HEADER Internal Table
 SPLIT P_DOWNLOAD AT ',' INTO
 IT_DATA_HEADER-ID
 IT_DATA_HEADER-BUKRS
 IT_DATA_HEADER-WAERS
 IT_DATA_HEADER-NEWKO
 IT_DATA_HEADER-XBLNR
 IT_DATA_HEADER-XBLNR1
 IT_DATA_HEADER-BLDAT
 IT_DATA_HEADER-PK
 IT_DATA_HEADER-WRBTR
 IT_DATA_HEADER-BKTXT
 IT_DATA_HEADER-BKTXT1.
 IT_DATA_HEADER-SELNO = V_SELNO.
 CONDENSE : IT_DATA_HEADER-ID, IT_DATA_HEADER-BUKRS,
 IT_DATA_HEADER-WAERS, IT_DATA_HEADER-NEWKO,
 IT_DATA_HEADER-XBLNR, IT_DATA_HEADER-XBLNR1,
 IT_DATA_HEADER-BLDAT, IT_DATA_HEADER-PK,
 IT_DATA_HEADER-WRBTR, IT_DATA_HEADER-BKTXT,
 IT_DATA_HEADER-BKTXT1, IT_DATA_HEADER-SELNO.
 APPEND IT_DATA_HEADER.
 CLEAR IT_DATA_HEADER.
 ELSEIF P_DOWNLOAD(1) = '2'.
Moving header information into IT_DATA_ITEM Internal Table
 SPLIT P_DOWNLOAD AT ',' INTO
 IT_DATA_ITEM-ID
 IT_DATA_ITEM-NEWKO
 IT_DATA_ITEM-BUKRS
 IT_DATA_ITEM-KOSTL
 IT_DATA_ITEM-WRBTR
 IT_DATA_ITEM-SGTXT.
 IT_DATA_ITEM-SELNO = V_SELNO.
 IT_DATA_ITEM-SELNO1 = SY-TABIX.
 CONDENSE: IT_DATA_ITEM-ID,IT_DATA_ITEM-NEWKO,IT_DATA_ITEM-BUKRS,
 IT_DATA_ITEM-KOSTL,IT_DATA_ITEM-WRBTR,
 IT_DATA_ITEM-SGTXT,IT_DATA_ITEM-SELNO,
 IT_DATA_ITEM-SELNO1.
 APPEND IT_DATA_ITEM.
 CLEAR IT_DATA_ITEM.
 ENDIF.
 ENDLOOP.
*SORT HEADER & ITEM INTERNAL Table
 SORT IT_DATA_HEADER BY SELNO.
 SORT IT_DATA_ITEM BY SELNO SELNO1.
*Header Information
 LOOP AT IT_DATA_HEADER.
 IT_FINAL_HEADER-ID = IT_DATA_HEADER-ID.
 IT_FINAL_HEADER-BUKRS = IT_DATA_HEADER-BUKRS.
 IT_FINAL_HEADER-WAERS = IT_DATA_HEADER-WAERS.
 IT_FINAL_HEADER-NEWKO = IT_DATA_HEADER-NEWKO.
 CONCATENATE IT_DATA_HEADER-XBLNR IT_DATA_HEADER-XBLNR1
 INTO IT_FINAL_HEADER-XBLNR.
 IT_FINAL_HEADER-BLDAT = IT_DATA_HEADER-BLDAT.
 IT_FINAL_HEADER-PK = IT_DATA_HEADER-PK.
 IT_FINAL_HEADER-WRBTR = IT_DATA_HEADER-WRBTR.
 IT_FINAL_HEADER-BKTXT = IT_DATA_HEADER-BKTXT.
 IT_FINAL_HEADER-BKTXT1 = IT_DATA_HEADER-BKTXT1.
 IT_FINAL_HEADER-SELNO = IT_DATA_HEADER-SELNO.
 APPEND IT_FINAL_HEADER.
 CLEAR IT_FINAL_HEADER.
 ENDLOOP.
*Item Information
 LOOP AT IT_DATA_ITEM.
CHECKING ZERO IN THE IT_DATA_ITEM-WRBTR FIELD
It will not append the IT_FINAL_ITEM
 V_CHECK_ZERO = IT_DATA_ITEM-WRBTR.
 IF V_CHECK_ZERO NE V_CHECK_ZERO1. "V_ZERO.
 IT_FINAL_ITEM-ID = IT_DATA_ITEM-ID.
 IT_FINAL_ITEM-NEWKO = IT_DATA_ITEM-NEWKO.
 IT_FINAL_ITEM-BUKRS = IT_DATA_ITEM-BUKRS.
 IT_FINAL_ITEM-KOSTL = IT_DATA_ITEM-KOSTL.
 IT_FINAL_ITEM-WRBTR = IT_DATA_ITEM-WRBTR.
 IT_FINAL_ITEM-SGTXT = IT_DATA_ITEM-SGTXT.
 IT_FINAL_ITEM-SELNO = IT_DATA_ITEM-SELNO.
 IT_FINAL_ITEM-SELNO1 = IT_DATA_ITEM-SELNO1.
 APPEND IT_FINAL_ITEM.
 CLEAR IT_FINAL_ITEM.
 CLEAR : V_CHECK_ZERO,V_CHECK_ZERO1.
 ENDIF.
 ENDLOOP.
 SORT IT_FINAL_HEADER BY SELNO.
 SORT IT_FINAL_ITEM BY SELNO.
ENDIF.
ENDFORM. " UPLOAD_DATA
*& Form MOVE_DATA_F43
 Call Transaction F-43
FORM MOVE_DATA_F43.
*MOVE THE SYSTEM DATE TO
CLEAR V_SYSTEMDATE.
V_SYSTEMDATE = SY-DATUM.
LOOP AT IT_FINAL_HEADER.
 CLEAR V_CHECK.
 V_CHECK = IT_FINAL_HEADER-SELNO.
MOVE HEADER DATA TO BDCDATA INTERNAL TABLE
 PERFORM BDC_BUILD_HEADER.
MOVE ITEM DATA TO BDCDATA INTERNAL TABLE
 PERFORM BDC_BUILD_ITEM.
* Call Transcation (F-43)
 CALL TRANSACTION 'F-43' USING IT_BDCDATA
 MODE XMODE
 UPDATE 'S'
 MESSAGES INTO IT_MESSAGE_TAB.
IF error record found, it will move to batch Input session
 IF SY-SUBRC <> 0.
 V_ERROR_COUNTER = V_ERROR_COUNTER + 1. " Inc the counter
 CLEAR V_LINES.
 DESCRIBE TABLE IT_MESSAGE_TAB LINES V_LINES.
 READ TABLE IT_MESSAGE_TAB INDEX V_LINES.
*--- Perform to read the messages
 PERFORM MESSAGE_FORMAT.*--- Appending the error records into error table
 CONDENSE IT_FINAL_HEADER-BUKRS.
 CONDENSE IT_FINAL_HEADER-NEWKO.
 CONDENSE IT_FINAL_HEADER-XBLNR.
 CONDENSE IT_FINAL_HEADER-BLDAT.
 CONCATENATE IT_FINAL_HEADER-BUKRS ','
 IT_FINAL_HEADER-NEWKO ','
 IT_FINAL_HEADER-XBLNR ','
 IT_FINAL_HEADER-BLDAT
 INTO V_HEADER.
 I_ERROR_LOG-HEADER = V_HEADER.
 I_ERROR_LOG-MSG = V_MSG.
 APPEND I_ERROR_LOG.
 CLEAR I_ERROR_LOG.
*-- Posting the error record to Session
 IF F_BDC_OPEN IS INITIAL.
 PERFORM OPEN_SESSION.
 ENDIF.
 PERFORM BDC_INSERT USING 'F-43'.
 ELSE.
 V_SUCCESS_COUNTER = V_SUCCESS_COUNTER + 1.
*-- READING ONLY SUCCESS MESSAGE(MSGNR 312)
 LOOP AT IT_MESSAGE_TAB WHERE MSGNR = '312'.
 V_SUCC_MSG = IT_MESSAGE_TAB-MSGV1.
 ENDLOOP.
*--- Perform to read the messages
 PERFORM MESSAGE_FORMAT.
*--- Appending the Success records into Success table
 CONDENSE IT_FINAL_HEADER-BUKRS.
 CONDENSE IT_FINAL_HEADER-NEWKO.
 CONDENSE IT_FINAL_HEADER-PK.
 CONDENSE IT_FINAL_HEADER-XBLNR.
 CONDENSE IT_FINAL_HEADER-BLDAT.
 CONCATENATE IT_FINAL_HEADER-BUKRS ','
 IT_FINAL_HEADER-NEWKO ','
 IT_FINAL_HEADER-PK ','
 IT_FINAL_HEADER-XBLNR ','
 IT_FINAL_HEADER-BLDAT
 INTO V_HEADER.
 I_SUCC-HEADER = V_HEADER.
 I_SUCC-MSG = V_SUCC_MSG.
 APPEND I_SUCC.
 CLEAR I_SUCC.
 ENDIF.
 V_TOTAL = V_TOTAL + 1.
 REFRESH: IT_BDCDATA,
 IT_MESSAGE_TAB.
 CLEAR: IT_BDCDATA,
 IT_MESSAGE_TAB.
ENDLOOP.
ENDFORM. " MOVE_DATA_F43
 Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = DYNPRO.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.
ENDFORM.
 Insert field *
FORM BDC_FIELD USING FNAM FVAL.
CLEAR IT_BDCDATA.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.
ENDFORM.
*& Form BDC_BUILD_HEADER
 Header Information
FORM BDC_BUILD_HEADER.
Header Details
PERFORM BDC_DYNPRO USING 'SAPMF05A' '0100'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_FIELD USING 'BKPF-BLDAT'
 IT_FINAL_HEADER-BLDAT.
PERFORM BDC_FIELD USING 'BKPF-BLART'
 'KR'.
PERFORM BDC_FIELD USING 'BKPF-BUKRS'
 IT_FINAL_HEADER-BUKRS.
Moveing System date to Posting date in the document
CLEAR IT_FINAL_HEADER-BLDAT.
CONCATENATE V_SYSTEMDATE4(4) V_SYSTEMDATE0(4)
 INTO IT_FINAL_HEADER-BLDAT.
PERFORM BDC_FIELD USING 'BKPF-BUDAT'
 IT_FINAL_HEADER-BLDAT.
PERFORM BDC_FIELD USING 'BKPF-WAERS'
 IT_FINAL_HEADER-WAERS.
PERFORM BDC_FIELD USING 'BKPF-XBLNR'
 IT_FINAL_HEADER-PK.
PERFORM BDC_FIELD USING 'BKPF-BKTXT'
 IT_FINAL_HEADER-BKTXT.
PERFORM BDC_FIELD USING 'FS006-DOCID' '*'.
IF IT_FINAL_HEADER-WRBTR CA '-'.
 REPLACE '-' WITH SPACE INTO IT_FINAL_HEADER-WRBTR.
 CONDENSE IT_FINAL_HEADER-WRBTR.
 PERFORM BDC_FIELD USING 'RF05A-NEWBS' '25'.
ELSE.
 PERFORM BDC_FIELD USING 'RF05A-NEWBS' '31'.
ENDIF.
PERFORM BDC_FIELD USING 'RF05A-NEWKO'
 IT_FINAL_HEADER-NEWKO.
*-- Item Vendor Details
PERFORM BDC_DYNPRO USING 'SAPMF05A' '0302'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
PERFORM BDC_FIELD USING 'BSEG-WRBTR'
 IT_FINAL_HEADER-WRBTR.
PERFORM BDC_FIELD USING 'BSEG-SGTXT'
 IT_FINAL_HEADER-BKTXT1.
ENDFORM. " BDC_BUILD_HEADER
*& Form BDC_BUILD_ITEM
 Item Information
FORM BDC_BUILD_ITEM.
DATA L_FIRST TYPE C.
LOOP AT IT_FINAL_ITEM WHERE SELNO = V_CHECK.
 IF L_FIRST IS INITIAL.
 L_FIRST = C_X.
Line Item ( PstKy,Account & New Company Code)
 CONDENSE IT_FINAL_HEADER-BLDAT.
 IF IT_FINAL_ITEM-WRBTR CA '-'.
 REPLACE '-' WITH SPACE INTO IT_FINAL_ITEM-WRBTR.
 CONDENSE IT_FINAL_ITEM-WRBTR.
 PERFORM BDC_DYNPRO USING 'SAPMF05A' '0302'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' '/00',
 'RF05A-NEWBS' '50',
 'RF05A-NEWKO' IT_FINAL_ITEM-NEWKO,
 'RF05A-NEWBK' IT_FINAL_ITEM-BUKRS.
 ELSE.
 PERFORM BDC_DYNPRO USING 'SAPMF05A' '0302'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' '/00',
 'RF05A-NEWBS' '40',
 'RF05A-NEWKO' IT_FINAL_ITEM-NEWKO,
 'RF05A-NEWBK' IT_FINAL_ITEM-BUKRS.
 ENDIF.
Amount & Text
 PERFORM BDC_DYNPRO USING 'SAPMF05A' '0300'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' '/00',
 'BSEG-WRBTR' IT_FINAL_ITEM-WRBTR,
 'BSEG-SGTXT' IT_FINAL_ITEM-SGTXT,
 'DKACB-FMORE' 'X'.
Cost Center
 PERFORM BDC_DYNPRO USING 'SAPLKACB' '0002'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' 'ENTE',
 'COBL-KOSTL' IT_FINAL_ITEM-KOSTL.
 ELSE.
Line Item ( PstKy,Account & New Company Code)
 IF IT_FINAL_ITEM-WRBTR CA '-'.
 REPLACE '-' WITH SPACE INTO IT_FINAL_ITEM-WRBTR.
 CONDENSE IT_FINAL_ITEM-WRBTR.
 PERFORM BDC_DYNPRO USING 'SAPMF05A' '0300'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' '/00',
 'RF05A-NEWBS' '50',
 'RF05A-NEWKO' IT_FINAL_ITEM-NEWKO,
 'RF05A-NEWBK' IT_FINAL_ITEM-BUKRS.
 ELSE.
 PERFORM BDC_DYNPRO USING 'SAPMF05A' '0300'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' '/00',
 'RF05A-NEWBS' '40',
 'RF05A-NEWKO' IT_FINAL_ITEM-NEWKO,
 'RF05A-NEWBK' IT_FINAL_ITEM-BUKRS.
 ENDIF.
 PERFORM BDC_DYNPRO USING 'SAPLKACB' '0002'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' 'ENTE'.
Amount & Text
 PERFORM BDC_DYNPRO USING 'SAPMF05A' '0300'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' '/00',
 'BSEG-WRBTR' IT_FINAL_ITEM-WRBTR,
 'BSEG-SGTXT' IT_FINAL_ITEM-SGTXT,
 'DKACB-FMORE' 'X'.
Cost Center
 PERFORM BDC_DYNPRO USING 'SAPLKACB' '0002'.
 PERFORM BDC_FIELD USING: 'BDC_OKCODE' 'ENTE',
 'COBL-KOSTL' IT_FINAL_ITEM-KOSTL.
 ENDIF.
ENDLOOP.
*Save Details
PERFORM BDC_DYNPRO USING 'SAPMF05A' '0300'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=BU'.
PERFORM BDC_DYNPRO USING 'SAPLKACB' '0002'.
PERFORM BDC_FIELD USING: 'BDC_OKCODE' 'ENTE'.
ENDFORM. " BDC_BUILD_ITEM
Thanks
Mahesh

How to find a badi and how to find the method/methods for a transaction?

Hi all,
i need to give a text either while creating customer (vd01) or changing customer(vd02)...thsi is via extras->texts.....then I have to double clik the text and go to change editor...and then i have to clik on insert line and then choose text element radiobutton on screen and then give it a name and then save it..this should be done for all customers....my problem is i am unable to find a badi and the appropriate method for thsi..i have placed break point in method read_add_on_data in the badi customer_add_data....i tested both by transactions va01 and va02 but of no use..also there are so many methods..can u tell me how do i find the appropriate method of the appropriate badi.....

Hi,
For XD01/XD02/XD03 The following BADI's are useful
business Add-In CUSTOMER_ADD_DATA and business Add-In CUSTOMER_ADD_DATA_CS .
*Reward points
Regards

How to get the sms history for iphone 4S

Hello,
I would like some help to find out how to ressurect the message history for messages that I have received on my phone and never backed up anywhere. The messages have dissapeared by themselves, without having me deleting them or changing any default settings. Please help me to get the message history back.
With regards,
Caroline

Apple does not sell parts. You may be able to find something out there, but what you will get is either something stripped from a damaged phone, a knockoff, or marginal parts that failed factory inspection and are now being illegaly sold.

Does anyone know how to delete the back up for the ipod? I am getting an error message that says "iTunes could not back up iPod because it is corrupt or not compatible with iPod; delete back up and try again"

does anyone know how to delete the back up for the ipod? I am getting an error message that says "iTunes could not back up iPod because it is corrupt or not compatible with iPod; delete back up and try again"

Go to iTunes>Preferences>Devices and highlight the backup you want to delete and click on Delete Backup

How to keep the field open for input with error message in report program

Hi,
Need a help in solving the below issue.
"How to keep the field open for input with error message in report program"
Regards,
C.Shasiraj.

Hi...
you have to use the event:
AT SELECTION-SCREEN ON <FIELD> EVENT.
u have to give an error message in this event.
Consider the following Example:
PARAMETERS : NUMBER TYPE I.
AT SELECTION-SCREEN ON NUMBER.
IF NUMBER = 10.
MESSAGE 'Number vakue is 10' TYPE 'E'.
ENDIF.
START-OF-SELECTION.
WRITE NUMBER.

in this if u give the value of number = 10, it will not proceed further, if u give some other value other than 10 you will proceed further...
Execute this program once u will understand....
also Consider the following links :
Regarding events:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/79/34a237d9b511d1950e0000e8353423/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/79/34a23ad9b511d1950e0000e8353423/frameset.htm
Regarding messages:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/aa575426ad11d2954d0000e8353423/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/aa575426ad11d2954d0000e8353423/frameset.htm
This is very useful.......
Reward points if useful....
Suresh....

How to know the function module for a message type

hi sd gurus,
how can i know the function modules used ( based on message type can i know it?) in inbound idoc processing.
can anyone let me know where can i find it out and the related transaction codes
Thanks&Regards
Srini

You can find out the Functionmodule if you know the message type.
Go to WE20, find the message type for hte relevant partner type by clicking the partner type and then clicking one partner int hat partner type.
Now on the right hand side, you will get a screen. Based on whether it is your outbound IDOC or ibound, click the relevant parameters, select the message type and double click.
In the new screen open the Message control tab and fidn out the process code of the IDOC.
Now go to WE41 if ur IDOC is outbound or WE42 for inbound IDOC.
Search for the process code which is assigned to the message type in WE20.
Double click the process code, you will see the relevant function module in the 3rd field.
Hope thsi helps you
Pls reward if it helps.

How to verify the message id for call transaction ?

Similar Messages

Maybe you are looking for