IDOC or BAPI to use to upload timekeeping and labor schedule to SAP HCM

Hi guys!
We would like to upload timekeeping and labor schedule data from a database to SAP HCM.
For me to accomplish that, what BAPI or IDOC can I use to upload the following:
1) Timekeeping data
2) Labor Schedule.
Thanks!
Regards,
Jonathan

Hi,
I too need to find IDOC for MEBI transaction.
Didi you find any IDOC for it?
Smriti

Similar Messages

File upload using commons-upload-file and tomcat 5.5

Hi,
This is my first post and I hope that I post it at the right place.
I'm trying to upload a file using commons-upload-file and tomcat 5.5.
Is there a way to prevent submitting a big file, If I detect that the file being uploaded exceed a limit that I have fixed ?
i.e. I check the request length, if it's bigger than 1meg I cancel the whole thing and the big file is not transferred.
The problem that I get at the moment is that it seems that the file is transferred even if I close request inputstream or response outputstream. Any help would be appreciated !
Thank you
Redgy

Well here is a snippet of my code:
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException {
        long maxSize = 50000;
        boolean isMultipart = ServletFileUpload.isMultipartContent(request);
        if(isMultipart){
            // Create a new file upload handler
            ServletFileUpload upload = new ServletFileUpload();
            upload.setSizeMax(maxSize);
            try {
                upload.parseRequest(request);
            } catch (FileUploadException ex) {
                ex.printStackTrace();
                request.getInputStream().close();
                response.getWriter().print("blah");
                response.sendError(response.SC_INTERNAL_SERVER_ERROR);
                response.getOutputStream().close();
    }If the file is bigger than 50kb, it Throws the FileUploadException.
But whatever I do, It seems that there is still a connection between my browser and tomcat.. any clue ?
thanks
Edited by: redgyx on Jan 31, 2008 6:17 AM

Using ABAP Webdynpr How to Upload File and download file in SAP R/3

Hi SAP GURUS ,
                         I wanted to save employee profile from ESS to SAP so i am creating ESS Application .
For that I go with BDS Approach and create test program for this I got success while uploading file in my folder
which i have created with the help of class and content repository . but when i Using ABAP Webdynpro , i got error FM "BDS_BUSINESSDOCUMENT_CREATEF" message " error_kpro " .
                       Also I wanted to use KM for storage of Documents and wanted to retrive with help of ABAP Webdynpro .
                       So pls tell me / mailed me the process , approach and if you have examples .
    Thanks in Advance ,
     Vishwassap at gmail

Hi Vishwas,
Check out the thread [Efficient way of saving documents uploaded|Re: Efficient way of saving documents uploaded by users; and check the blog by Raja Thangamani.
Also check the thread [Export Images through Function Modules   |Export Images through Function Modules;.
Hope it helps you.

BAPI's for creating of Project and WBS elements in SAP system.

Hi Guys,
             I was able to use a Wrapper FM for creating the
We have a FM which combines 5 different BAPIs
FM/Wrapper: "Z_LEED_PROJ_WBSELEMT_CREATE"
1)      BAPI_PS_INITIALIZATION
2)      BAPI_BUS2001_CREATE
3)      BAPI_BUS2054_CREATE_MULTI
4)      BAPI_PS_PRECOMMIT
5)      BAPI_TRANSACTION_COMMIT
Requirement: To automate the process of creation of Project and WBSE(Tasks) and create an entries in the PS tables based on the user inputs from the user interface in Visual Composer.
Basically user should be able to create the Projects and WBSE.
Issue: We were able to create the Project with the FM (BAPI_BUS2001_CREATE) but having the issue with the creation of WBSE(Tasks), the user will be entering the inputs for Project Definition, Project Profile and WBSE which are to be created in the UI.
The problem is we are not able to create the WBS elements using BAPI     BAPI_BUS2054_CREATE_MULTI .i will send u the code below .Can anybody correct
   CLEAR it_return.
CALL FUNCTION 'BAPI_BUS2054_CREATE_MULTI'
    EXPORTING
      I_PROJECT_DEFINITION = i_project_definition-project_definition
    TABLES
      IT_WBS_ELEMENT = it_wbs_element
      ET_RETURN = it_return.
APPEND LINES OF it_return[] TO et_return[].
Thanks,
Gopi.

Hi Ramiro,
               This is the entire FM code which is below.
""Local Interface:
*" IMPORTING
*"     VALUE(I_PROJECT_DEFINITION) LIKE BAPI_BUS2001_NEW STRUCTURE
*"        BAPI_BUS2001_NEW
*" TABLES
*"      IT_WBS_ELEMENT STRUCTURE BAPI_BUS2054_NEW
*"      ET_RETURN STRUCTURE BAPIRET2 OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      EXTENSIONOUT STRUCTURE BAPIPAREX OPTIONAL
DATA: it_return LIKE STANDARD TABLE OF BAPIRET2 WITH HEADER LINE,
        v_error TYPE boolean VALUE IS INITIAL.
CLEAR: et_return, it_return.
CALL FUNCTION 'BAPI_PS_INITIALIZATION'.
Do checks for creating project definition
CALL FUNCTION 'BAPI_BUS2001_CREATE'
    EXPORTING
      I_PROJECT_DEFINITION = i_project_definition
    TABLES
      ET_RETURN = it_return.
APPEND LINES OF it_return[] TO et_return[].
LOOP AT it_return.
    IF it_return-type CA 'EAX'.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      v_error = 'X'.
      EXIT.
    ENDIF.
ENDLOOP.
IF v_error = 'X'.
    EXIT.
ENDIF.
Do checks for creating WBS elements
CLEAR it_return.
CALL FUNCTION 'BAPI_BUS2054_CREATE_MULTI'
    EXPORTING
      I_PROJECT_DEFINITION = i_project_definition-project_definition
    TABLES
      IT_WBS_ELEMENT = it_wbs_element
      ET_RETURN = it_return.
   APPEND LINES OF it_return[] TO et_return[].
LOOP AT it_return.
    IF it_return-type CA 'EAX'.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      v_error = 'X'.
      EXIT.
    ENDIF.
ENDLOOP.
IF v_error = 'X'.
    EXIT.
ENDIF.
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
    TABLES
      ET_RETURN = it_return.
   APPEND LINES OF it_return[] TO et_return[].
LOOP AT it_return.
    IF it_return-type CA 'EAX'.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      v_error = 'X'.
      EXIT.
    ENDIF.
ENDLOOP.
IF v_error = 'X'.
    EXIT.
ENDIF.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      WAIT = 'X'.
ENDFUNCTION.
can u please look at the code and let me know the changes?
Thanks,
Gopi.

Use of work shifts and time schedules if there is no attendance capturing

hi all
what is the need for creating work shifts and time schedules , if there is no attendance capturing sysgtem in time management.Its quite necessary and hopes yours answer asap.
M Swadhin

Hi
Thanks for your reply. further i want to say :
My client requirement is In time and out time maintaining in Negative time management. Is it possible ? ? ? ?
can we maintain in time and out time in negative time mgt through some external devices or any other way.
your reply would be appreciable.
thanks
Swadhin

Mass Upload - ALE/IDOC or BAPI approch

Hi Guys,
I have to upload material master and we have options to do it by either ALE/IDOC or BAPI approach. The quantity of materials is quite huge. I tried to find some comparison about different approaches so as to know when to use what but not able to get exact information. Kindly suggest which one is usually preferred for mass upload and if possible provide some links for more references.
Thanks,
Brijesh Soni

I have never seen such recomendations or benchmarks
SAP has a homepage for benchmarks: http://www.sap.com/solutions/benchmark/index.epx
the source is the same, then result is the same. all steps in LSMW are the same. you have to map the same fields in any method.
BAPI may have some more structures than IDOC or batch input. so just minutes more to assign the source structure to the target structure. .
it is a historical growth or development. It started with batch input to process SAP transactions en mass
then the IDOCs came to exchange data between 2 SAP systems.
and then we got the BAPIs to execute SAP transactions even from a non-sap system.
the result is in all three methods a created material master.
LSMW is a toolbox which gives you any of the available import methods.
there are other aspects to be considered in a migration.
What if you have errors? do you correct them yourself, or do you want the business people to fix them.
if you want business people to fix wrong data, then a batch import method may be the first option, as you can process it in foreground. It is too much complicated for a Non-IT-person to edit values in IDOCs. (even the performance may be better than a batch input)

How to Use PM BAPI for equipment Master upload : BAPI_EQUIPMENT_SAVEREPLICA

Hi ,
How to use PM BAPI for equipment Master upload : BAPI_EQUIPMENT_SAVEREPLICA.
May i know what are the input parameters & fields mandatory
for each Table structures ct_data , ct_datax , it_descript , it_longtext.
Can any one explain me Step by Step Process.
B'cos i tried with below code. Equipment is not getting created.
wa_itab-equipment_ext = '000000000100000001'.
wa_itab-descript      = 'Test 2 -> Lube Oil Pump'.
wa_itab-text_language = 'EN'.
wa_itab-sdescript     = 'Short Description'.
APPEND wa_itab TO it_itab.
CLEAR wa_itab.
LOOP AT it_itab INTO wa_itab.
    ct_data-ta_guid       = '000000000000000001'.
    ct_data-equipment_ext = wa_itab-equipment_ext.
    ct_data-descript      = wa_itab-descript     .
    ct_data-valid_date    = sy-datum.
    ct_data-equicatgry    = 'M'.
    APPEND ct_data.
    CLEAR ct_data.
    ct_datax-ta_guid       = '000000000000000001'.
    ct_datax-equipment_ext = 'X'.
    ct_datax-equipment     = 'X'.
    APPEND ct_datax.
    CLEAR ct_datax.
    it_descript-ta_guid       = '000000000000000001'.
    it_descript-text_language = wa_itab-text_language.
    it_descript-descript      = wa_itab-sdescript    .
    APPEND it_descript.
    CLEAR it_descript.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'LTXT'.
    it_longtext-text_line      = 'SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'aaaaaaaaaaaaaaa'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'bbbbbbbbbbbb'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'cccccccccccccccc'.
    APPEND it_longtext.
    CLEAR it_longtext.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
call BAPI-function in this system
    CALL FUNCTION 'BAPI_EQUIPMENT_SAVEREPLICA'
      TABLES
        ct_data     = ct_data
        ct_datax    = ct_datax
        it_descript = it_descript
        it_longtext = it_longtext
        return      = return
      EXCEPTIONS
        OTHERS      = 1.
    IF sy-subrc = 0.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      WRITE : 'Successful'.
    ENDIF.
    IF NOT return IS INITIAL.
      LOOP AT return.
        IF return-type = 'A' OR return-type = 'E'.
          WRITE : 'Error'.
        ENDIF.
      ENDLOOP.
    ENDIF.
    REFRESH return.
ENDLOOP.
Regards
SUrendar

Hi ,
How to use PM BAPI for equipment Master upload : BAPI_EQUIPMENT_SAVEREPLICA.
May i know what are the input parameters & fields mandatory
for each Table structures ct_data , ct_datax , it_descript , it_longtext.
Can any one explain me Step by Step Process.
B'cos i tried with below code. Equipment is not getting created.
wa_itab-equipment_ext = '000000000100000001'.
wa_itab-descript      = 'Test 2 -> Lube Oil Pump'.
wa_itab-text_language = 'EN'.
wa_itab-sdescript     = 'Short Description'.
APPEND wa_itab TO it_itab.
CLEAR wa_itab.
LOOP AT it_itab INTO wa_itab.
    ct_data-ta_guid       = '000000000000000001'.
    ct_data-equipment_ext = wa_itab-equipment_ext.
    ct_data-descript      = wa_itab-descript     .
    ct_data-valid_date    = sy-datum.
    ct_data-equicatgry    = 'M'.
    APPEND ct_data.
    CLEAR ct_data.
    ct_datax-ta_guid       = '000000000000000001'.
    ct_datax-equipment_ext = 'X'.
    ct_datax-equipment     = 'X'.
    APPEND ct_datax.
    CLEAR ct_datax.
    it_descript-ta_guid       = '000000000000000001'.
    it_descript-text_language = wa_itab-text_language.
    it_descript-descript      = wa_itab-sdescript    .
    APPEND it_descript.
    CLEAR it_descript.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'LTXT'.
    it_longtext-text_line      = 'SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'aaaaaaaaaaaaaaa'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'bbbbbbbbbbbb'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'cccccccccccccccc'.
    APPEND it_longtext.
    CLEAR it_longtext.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
call BAPI-function in this system
    CALL FUNCTION 'BAPI_EQUIPMENT_SAVEREPLICA'
      TABLES
        ct_data     = ct_data
        ct_datax    = ct_datax
        it_descript = it_descript
        it_longtext = it_longtext
        return      = return
      EXCEPTIONS
        OTHERS      = 1.
    IF sy-subrc = 0.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      WRITE : 'Successful'.
    ENDIF.
    IF NOT return IS INITIAL.
      LOOP AT return.
        IF return-type = 'A' OR return-type = 'E'.
          WRITE : 'Error'.
        ENDIF.
      ENDLOOP.
    ENDIF.
    REFRESH return.
ENDLOOP.
Regards
SUrendar

Using BAPI functions BSP file upload

Hello,
Can anyone clarify me that ' can I upload a file form front end using BSP to the BP as backend to store e the image using the BAPI functions. All this is to get each BP photo in the Solution manager.
or I have use the datasets for the file upload. Please help me out.
With best regards,
Suneetha

Hi,
Uploading LOGO in SAP
http://www.sap-img.com/ts001.htm
Upload graphics on
The program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into individual standard text.
ws_upload
Transfer files from the frontend to the application server.
Rgds,
Prakash

Hello ! pls give some ti[ps how to use bapi's for data uploading?

hello !
pls give some ti[ps how to use bapi's for data uploading?
regards,
Arjun

Hi,
See the below report extract:
where it_data is having uploaded data.
LOOP AT it_data INTO wa_data.
 line_count = sy-tabix.
 "Date Validation
 CONCATENATE wa_data-uplft_date4(4) wa_data-uplft_date2(2) wa_data-uplft_date+0(2)
 INTO wa_data-uplft_date.
 "READ TABLE it_ekko INTO wa_ekko WITH KEY lifnr = wa_data-vendor.
 LOOP AT it_ekko_temp INTO wa_ekko_temp WHERE lifnr = wa_data-vendor.
 IF wa_ekko_temp-kdatb <= wa_data-uplft_date AND wa_ekko_temp-kdate >= wa_data-uplft_date.
 MOVE-CORRESPONDING wa_ekko_temp TO wa_ekko.
 APPEND wa_ekko TO it_ekko.
 ENDIF.
 ENDLOOP.
 "IF sy-subrc = 0 AND wa_ekko-kdatb <= wa_data-uplft_date AND wa_ekko-kdate >= wa_data-uplft_date.
 LOOP AT it_ekko INTO wa_ekko.
 wa_data_header-pstng_date = wa_data-uplft_date.
 wa_data_header-doc_date = sy-datum.
 wa_data_header-bill_of_lading = wa_data-bill_of_lad.
 wa_data_header-ref_doc_no = wa_data-del_no.
 CONCATENATE wa_data-header_text1 '-'
 wa_data-header_text2 '-'
 wa_data-header_text3 '-'
 wa_data-header_text4
 into wa_data_header-HEADER_TXT.
 IF wa_data-indicator = 'Y'.
 wa_data_item-material = '000000000000200568'.
 ELSE.
 wa_data_item-material = '000000000000200566'.
 ENDIF.
 LOOP AT it_ekpo INTO wa_ekpo WHERE ebeln = wa_ekko-ebeln AND matnr = wa_data_item-material.
 "Collect Item Level Data
 wa_data_item-plant = '1000'.
 wa_data_item-stge_loc = '1001'.
 wa_data_item-move_type = '101'.
 wa_data_item-vendor = wa_data-vendor.
 wa_data-qnty = wa_data-qnty / 1000.
 wa_data_item-entry_qnt = wa_data-qnty.
 wa_data_item-po_pr_qnt = wa_data-qnty.
 wa_data_item-entry_uom = 'KL'.
 wa_data_item-entry_uom_iso = 'KL'.
 wa_data_item-orderpr_un = 'KL'.
 wa_data_item-orderpr_un_iso = 'KL'.
 wa_data_item-no_more_gr = 'X'.
 wa_data_item-po_number = wa_ekpo-ebeln.
 wa_data_item-po_item = wa_ekpo-ebelp.
 wa_data_item-unload_pt = wa_data-unload_pt.
 wa_data_item-mvt_ind = 'B'.
 APPEND wa_data_item TO it_data_item.
 CLEAR wa_data_item.
 ENDLOOP.
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = wa_data_header
 goodsmvt_code = goodsmvt_code
 testrun = 'X'
 TABLES
 goodsmvt_item = it_data_item
 return = return.
 READ TABLE return INTO wa_return WITH KEY type = 'S'.
 IF sy-subrc <> 0.
 DESCRIBE TABLE return LINES sy-tfill.
 IF sy-tfill = 0.
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = wa_data_header
 goodsmvt_code = goodsmvt_code
 testrun = ' '
 TABLES
 goodsmvt_item = it_data_item
 return = return.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 WAIT = 'X'
 IMPORTING
 RETURN =
 ENDIF.
 ENDIF.
 LOOP AT return INTO wa_return.
 WRITE: 'Messsage TYPE ', wa_return-type,
 /,'ID ', wa_return-id,
 /, 'Number ', wa_return-number,
 /, 'Message ', wa_return-message,
 /, 'Long Text ', wa_return-message_v1,
 wa_return-message_v2,
 wa_return-message_v3,
 wa_return-message_v4,
 /, 'Failed at line', line_count.
 ENDLOOP.
 CLEAR: wa_ekko, wa_ekpo, wa_data, it_data_item[], wa_data_header.
 ENDLOOP.
Reward if useful!

Difference between lsmw using BAPI & lsmw using IDOC?

HI everybody
can anybody tell me difference between lsmw using BAPI & lsmw using IDOC?

IDocs and BAPI are very different, so it should be easy to choose between them depending on your requirements.
IDOCS
Advantages
System can work even if target system not always online. The IDoc will be created and sending will just continue once you get connected to the other system.
No additional programming required. You just need to set up the configuration.
Disadvantages
Receipt/processing on the target system may not be immediate.
The sending system has no way to know whether the target system actually received what you sent (unless you use ALE).
If there is no SAP standard IDoc available for your requirement, it's harder to create a customized IDoc than a customized BAPI.
BAPIS
Advantages
You can tell if your sending was successful or not
Sending to/processing on the other side is immediate
Easier to create your own BAPI than your own IDoc
Disadvantages
Will only work if you have an active online connection.
Some programming required to call the BAPI.
Others interface methods you might also want to consider are ALE and RFCs.

IDOC approach (Basic type : CREMAS01) to upload legacy vendors

I am using the IDOC approach (Basic type : CREMAS01) to upload legacy vendors.The LSMW then creates default partner functions.
However i need to modify the partner function.
My question is ...Is there a way to delete an entry through LSMW using IDOC approach (or even modify would help) but not append????
Thanks in advance ,
naval kishore bhatt.

Hi,
Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
Regards,
Gowri.S

Pros and Cons of using different uploads in LSMW

Hi,
I need to prepare a document, which specifies the pros and cons of migration using LSMW by different methods for a specific upload, where all the below options are available.
1) Batch Input
2) Direct Input
3) Idocs
4) BAPI
If anyone has prepared any document, can you pls send to me at [email protected] or give me some pointers.
Thanks in advance,
Ananth

Hi Kathirvel,
 I need to upload data into SAP using LSMW. I also need the document you sent to Anand. Please send it to me either at [email protected] or [email protected] will be a great help.
 One more thing Kathirvel, Can you help me find out how to Map flat legacy files to Hierarchical structures of SAP objects.(Flat file is having header record and list items).
 If you need more information please ask.
Thanks a lot,
Navdeep

IDoc or BAPI for inbound delivery creation with reference to PO.

Hi
I have requirement to create a inbound delivery, I will get a ASN from external system with PO, Vendor Material number & batch. I want to know is there any BAPI or IDoc that can be used to create inbound delivery in R/3. I used BBP_INB_DELIVERY_CREATE to create inbound delivery and I was successful but problem is that inbound delivery was not updated with Vendor Material number & Batch. Can some one suggest me any other BAPI or IDoc ?
Thanks in advance
Nagendra P Boggarapu
Edited by: Nagendra P Boggarapu on May 6, 2010 4:06 PM

Use Delvry0* IDOC.
Reddy

BAPI G/L Balance Upload

Hi,
I want BAPI for G/L balance upload.
I want to transfer these fields:
STYPE(BBKPF-STYPE)
LDGRP(BKPF-LDGRP)
BSCHL(Posting key)
MWSKZ(Tax Code)
I looked into BAPI's BAPI_ACC_GL_POSTING_POST and BAPI_ACC_DOCUMENT_POST but I didn't find any field like above fields.
Please suggest which BAPI to use so that I can get all the above fields. Better if someone can provide the code.
Thanks
Vinod.

Hi,
U can use Bapi "BAPI_ACC_DOCUMENT_POST" to post the G/L balances data.
Before that u need to activate the BADI "BADI_ACC_DOCUMENT".
This badi contains structure called "ACCIT" (Check the structure in SE11) which will fill the remaining fields which are not supported by BAPI.
For this u need to fill BAPI extension parameter. Check the bapi documentation for the procedure to fill the structure.

Automating Cash Journal Posting using inbound proxy interface and upload program

Hi Experts,
I have a requirement where in cash journal posting needs to be carried out automatically by an inbound interface on a periodic basis and at the start during cut over an upload program needs to be used to upload beg balance data . For this purpose I have used BAPI_CASHJOURNALDOC_CREATE to save cash journal entries along with BAPI TRANSACTION COMMIT.
Once the Data is successfully saved I am using FM FCJ_GET_DATA_FOR_SCREEN to get prerequisite data for the FM FCJ_POST_ALL which is used by the Standard cash journal program internally to post the saved data. ( I got this by debugging the standard transaction and both FMs are not yet released )
The issues I am facing is that the the FM FCJ_POST_ALL does not always post the data it behaves in random fashion i.e some times it posts the entries where as sometimes it does not post the entries.
I have tried using commit work after the FM but that also does not result in consistent behavior of the program. One more issue is the i am not allowed to use commit work in a an inbound proxy so how do i proceed ?
I am attaching the code for further analysis:
DATA: LIT_TCJ_TRANS_NAMES TYPE TABLE OF TCJ_TRANS_NAMES,
 LWA_TCJ_TRANS_NAMES TYPE TCJ_TRANS_NAMES,
 LV_WAIT TYPE BAPITA-WAIT VALUE '1',
 LV_RECORD_NO TYPE SY-TABIX.
 DATA : LIT_POSTING TYPE STANDARD TABLE OF ISCJ_POSTINGS,
 LIT_WTAX_ITEMS TYPE STANDARD TABLE OF TCJ_WTAX_ITEMS,
 LIT_SPLIT_POSTINGS TYPE STANDARD TABLE OF ISCJ_POSTINGS,
 LIT_CPD TYPE STANDARD TABLE OF TCJ_CPD.
 DATA: LV_BEG_BALANCE TYPE CJAMOUNT,
 LV_TOTAL_RECEIPTS TYPE CJAMOUNT,
 LV_TOTAL_PAYMENTS TYPE CJAMOUNT,
 LV_TOTAL_CHECKS TYPE CJAMOUNT,
 LV_RUN_BALANCE TYPE CJAMOUNT,
 LV_RUN_CASH_BALANCE TYPE CJAMOUNT,
 LV_NUMB_OF_REC TYPE I,
 LV_NUMB_OF_PAYM TYPE I,
 LV_NUMB_OF_CHECKS TYPE I.
 DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
 SELECT MANDT COMP_CODE TRANSACT_NUMBER LANGU TRANSACT_NAME LONG_TEXT
 FROM TCJ_TRANS_NAMES
 INTO TABLE LIT_TCJ_TRANS_NAMES
 WHERE LANGU = GC_EN.
 IF SY-SUBRC <> 0.
 MESSAGE 'No Business Transaction maintained for Company Code in this client'(016) TYPE GC_I.
 LEAVE LIST-PROCESSING.
 ENDIF.
 DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
 LOOP AT GIT_CJ INTO GWA_CJ.
 LV_RECORD_NO = SY-TABIX.
 CLEAR: GS_HEADER_BAPI,
 GS_CJ_KEY,
 GWA_ITEMS.
 REFRESH: GIT_ITEMS,
 GIT_RETURN.
 GS_HEADER_BAPI-COMP_CODE = GWA_CJ-BUKRS.
 GS_HEADER_BAPI-CAJO_NUMBER = GWA_CJ-CJNR.
 GS_HEADER_BAPI-CURRENCY = GC_PHP.
 CLEAR LWA_TCJ_TRANS_NAMES.
 READ TABLE LIT_TCJ_TRANS_NAMES INTO LWA_TCJ_TRANS_NAMES WITH KEY COMP_CODE = GWA_CJ-BUKRS
 LANGU = GC_EN
 TRANSACT_NAME = GWA_CJ-BTNAM.
 IF SY-SUBRC = 0.
 GWA_ITEMS-TRANSACT_NUMBER = LWA_TCJ_TRANS_NAMES-TRANSACT_NUMBER.
 GWA_ITEMS-P_RECEIPTS = GWA_CJ-CJRAT.
 GWA_ITEMS-TAX_CODE = GWA_CJ-TXCOD.
 GS_HEADER_BAPI-BP_NAME = GWA_CJ-BPNAM.
 GWA_ITEMS-POSITION_TEXT = GWA_CJ-POTXT.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-LIFNR
 IMPORTING
 OUTPUT = GWA_ITEMS-VENDOR_NO.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-KUNNR
 IMPORTING
 OUTPUT = GWA_ITEMS-CUSTOMER.
 PERFORM SUB_DATE_FROMAT_BAPI CHANGING GWA_CJ-BLDAT
 GS_HEADER_BAPI-DOC_DATE.
 PERFORM SUB_DATE_FROMAT_BAPI CHANGING GWA_CJ-BUDAT
 GS_HEADER_BAPI-PSTNG_DATE.
 GS_HEADER_BAPI-REF_DOC_NO = GWA_CJ-XBLNR.
 GS_HEADER_BAPI-ALLOC_NMBR = GWA_CJ-ALLNO.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-KOSTL
 IMPORTING
 OUTPUT = GWA_ITEMS-COSTCENTER.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-PRCTR
 IMPORTING
 OUTPUT = GWA_ITEMS-PROFIT_CTR.
 APPEND GWA_ITEMS TO GIT_ITEMS.
 CALL FUNCTION 'BAPI_CASHJOURNALDOC_CREATE'
 EXPORTING
 HEADER = GS_HEADER_BAPI
 IMPORTING
 COMPANY_CODE = GS_CJ_KEY-COMP_CODE
 CASH_JOURNAL_NUMBER = GS_CJ_KEY-CAJO_NUMBER
 FISCAL_YEAR = GS_CJ_KEY-FISC_YEAR
 CASH_JOURNAL_DOC_NO = GS_CJ_KEY-POSTING_NUMBER
 TABLES
 ITEMS = GIT_ITEMS
 RETURN = GIT_RETURN.
 IF GIT_RETURN IS NOT INITIAL.
 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_E.
 IF SY-SUBRC <> 0.
 CLEAR GWA_CJ_S.
 MOVE-CORRESPONDING GS_CJ_KEY TO GWA_CJ_S.
 CLEAR GWA_RETURN.
 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_S.
 IF SY-SUBRC = 0.
 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_S-MSG.
 CLEAR GWA_RETURN.
 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_I.
 IF SY-SUBRC = 0.
 CLEAR GWA_CJ_E.
 CONCATENATE GWA_RETURN-MESSAGE GWA_CJ_S-MSG INTO GWA_CJ_E-MSG SEPARATED BY GC_PIPE_FORMAT.
 MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
 GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
 APPEND GWA_CJ_E TO GIT_CJ_E.
 GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
 ELSE.
 IF P_TEST NE GC_X.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 WAIT = LV_WAIT.
 REFRESH:LIT_POSTING ,
 LIT_WTAX_ITEMS ,
 LIT_SPLIT_POSTINGS ,
 LIT_CPD .
 CLEAR: LV_BEG_BALANCE ,
 LV_TOTAL_RECEIPTS ,
 LV_TOTAL_PAYMENTS ,
 LV_TOTAL_CHECKS ,
 LV_RUN_BALANCE ,
 LV_RUN_CASH_BALANCE ,
 LV_NUMB_OF_REC ,
 LV_NUMB_OF_PAYM ,
 LV_NUMB_OF_CHECKS .
 CALL FUNCTION 'FCJ_GET_DATA_FOR_SCREEN'
 EXPORTING
 I_COMP_CODE = GS_CJ_KEY-COMP_CODE
 I_CAJO_NUMBER = GS_CJ_KEY-CAJO_NUMBER
 I_DISPLAY_PERIOD_LO = GS_HEADER_BAPI-PSTNG_DATE
 I_DISPLAY_PERIOD_HI = GS_HEADER_BAPI-PSTNG_DATE
 IMPORTING
 E_BEGINNING_BALANCE = LV_BEG_BALANCE
 E_RUNNING_BALANCE = LV_RUN_BALANCE
 E_RUNNING_CASH_BALANCE = LV_RUN_CASH_BALANCE
 E_TOTAL_RECEIPTS = LV_TOTAL_RECEIPTS
 E_TOTAL_REC_NUMBER = LV_NUMB_OF_REC
 E_TOTAL_PAYMENTS = LV_TOTAL_PAYMENTS
 E_TOTAL_PAYM_NUMBER = LV_NUMB_OF_PAYM
 E_TOTAL_CHECKS = LV_TOTAL_CHECKS
 E_TOTAL_CHECKS_NUMBER = LV_NUMB_OF_CHECKS
 TABLES
 E_POSTINGS = LIT_POSTING
 E_WTAX_ITEMS = LIT_WTAX_ITEMS
 E_SPLIT_POSTINGS = LIT_SPLIT_POSTINGS
 E_CPD = LIT_CPD.
 CALL FUNCTION 'FCJ_POST_ALL'
 EXPORTING
 I_COMP_CODE = GS_CJ_KEY-COMP_CODE
 I_CAJO_NUMBER = GS_CJ_KEY-CAJO_NUMBER
 I_CURRENCY = GS_HEADER_BAPI-CURRENCY
 I_TYP = 'R'
 I_DISPLAY_PERIOD_LO = GS_HEADER_BAPI-PSTNG_DATE
 I_DISPLAY_PERIOD_HI = GS_HEADER_BAPI-PSTNG_DATE
* IMPORTING
* E_ERROR_NUMBER =
 TABLES
 ITCJ_POSTINGS = LIT_POSTING
 ITCJ_WTAX_ITEMS = LIT_WTAX_ITEMS
 ITCJ_SPLIT_POSTINGS = LIT_SPLIT_POSTINGS
 ITCJ_CPD = LIT_CPD
 CHANGING
 P_BEG_BALANCE = LV_BEG_BALANCE
 P_TOTAL_RECEIPTS = LV_TOTAL_RECEIPTS
 P_TOTAL_PAYMENTS = LV_TOTAL_PAYMENTS
 P_TOTAL_CHECKS = LV_TOTAL_CHECKS
 P_RUN_BALANCE = LV_RUN_BALANCE
 P_RUN_CASH_BALANCE = LV_RUN_CASH_BALANCE
 P_NUMB_OF_REC = LV_NUMB_OF_REC
 P_NUMB_OF_PAYM = LV_NUMB_OF_PAYM
 P_NUMB_OF_CHECKS = LV_NUMB_OF_CHECKS.
 COMMIT WORK.
 ENDIF.
 APPEND GWA_CJ_S TO GIT_CJ_S.
 GV_SUCCESS_RECORDS = GV_SUCCESS_RECORDS + GC_1.
 CLEAR GWA_CJ_S.
 ENDIF.
 ENDIF.
 ELSE.
 CLEAR GWA_CJ_E.
 MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
 GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
 APPEND GWA_CJ_E TO GIT_CJ_E.
 GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
 ENDIF.
 ENDIF.
 ELSE.
 GWA_RETURN-MESSAGE = 'Transaction Name does not correspond to any Transaction Number'(017).
 CLEAR GWA_CJ_E.
 MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
 GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
 APPEND GWA_CJ_E TO GIT_CJ_E.
 GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
 ENDIF.
 ENDLOOP.
ENDFORM. " SUB_BAPI_CALL

Hi Experts,
I have a requirement where in cash journal posting needs to be carried out automatically by an inbound interface on a periodic basis and at the start during cut over an upload program needs to be used to upload beg balance data . For this purpose I have used BAPI_CASHJOURNALDOC_CREATE to save cash journal entries along with BAPI TRANSACTION COMMIT.
Once the Data is successfully saved I am using FM FCJ_GET_DATA_FOR_SCREEN to get prerequisite data for the FM FCJ_POST_ALL which is used by the Standard cash journal program internally to post the saved data. ( I got this by debugging the standard transaction and both FMs are not yet released )
The issues I am facing is that the the FM FCJ_POST_ALL does not always post the data it behaves in random fashion i.e some times it posts the entries where as sometimes it does not post the entries.
I have tried using commit work after the FM but that also does not result in consistent behavior of the program. One more issue is the i am not allowed to use commit work in a an inbound proxy so how do i proceed ?
I am attaching the code for further analysis:
DATA: LIT_TCJ_TRANS_NAMES TYPE TABLE OF TCJ_TRANS_NAMES,
 LWA_TCJ_TRANS_NAMES TYPE TCJ_TRANS_NAMES,
 LV_WAIT TYPE BAPITA-WAIT VALUE '1',
 LV_RECORD_NO TYPE SY-TABIX.
 DATA : LIT_POSTING TYPE STANDARD TABLE OF ISCJ_POSTINGS,
 LIT_WTAX_ITEMS TYPE STANDARD TABLE OF TCJ_WTAX_ITEMS,
 LIT_SPLIT_POSTINGS TYPE STANDARD TABLE OF ISCJ_POSTINGS,
 LIT_CPD TYPE STANDARD TABLE OF TCJ_CPD.
 DATA: LV_BEG_BALANCE TYPE CJAMOUNT,
 LV_TOTAL_RECEIPTS TYPE CJAMOUNT,
 LV_TOTAL_PAYMENTS TYPE CJAMOUNT,
 LV_TOTAL_CHECKS TYPE CJAMOUNT,
 LV_RUN_BALANCE TYPE CJAMOUNT,
 LV_RUN_CASH_BALANCE TYPE CJAMOUNT,
 LV_NUMB_OF_REC TYPE I,
 LV_NUMB_OF_PAYM TYPE I,
 LV_NUMB_OF_CHECKS TYPE I.
 DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
 SELECT MANDT COMP_CODE TRANSACT_NUMBER LANGU TRANSACT_NAME LONG_TEXT
 FROM TCJ_TRANS_NAMES
 INTO TABLE LIT_TCJ_TRANS_NAMES
 WHERE LANGU = GC_EN.
 IF SY-SUBRC <> 0.
 MESSAGE 'No Business Transaction maintained for Company Code in this client'(016) TYPE GC_I.
 LEAVE LIST-PROCESSING.
 ENDIF.
 DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
 LOOP AT GIT_CJ INTO GWA_CJ.
 LV_RECORD_NO = SY-TABIX.
 CLEAR: GS_HEADER_BAPI,
 GS_CJ_KEY,
 GWA_ITEMS.
 REFRESH: GIT_ITEMS,
 GIT_RETURN.
 GS_HEADER_BAPI-COMP_CODE = GWA_CJ-BUKRS.
 GS_HEADER_BAPI-CAJO_NUMBER = GWA_CJ-CJNR.
 GS_HEADER_BAPI-CURRENCY = GC_PHP.
 CLEAR LWA_TCJ_TRANS_NAMES.
 READ TABLE LIT_TCJ_TRANS_NAMES INTO LWA_TCJ_TRANS_NAMES WITH KEY COMP_CODE = GWA_CJ-BUKRS
 LANGU = GC_EN
 TRANSACT_NAME = GWA_CJ-BTNAM.
 IF SY-SUBRC = 0.
 GWA_ITEMS-TRANSACT_NUMBER = LWA_TCJ_TRANS_NAMES-TRANSACT_NUMBER.
 GWA_ITEMS-P_RECEIPTS = GWA_CJ-CJRAT.
 GWA_ITEMS-TAX_CODE = GWA_CJ-TXCOD.
 GS_HEADER_BAPI-BP_NAME = GWA_CJ-BPNAM.
 GWA_ITEMS-POSITION_TEXT = GWA_CJ-POTXT.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-LIFNR
 IMPORTING
 OUTPUT = GWA_ITEMS-VENDOR_NO.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-KUNNR
 IMPORTING
 OUTPUT = GWA_ITEMS-CUSTOMER.
 PERFORM SUB_DATE_FROMAT_BAPI CHANGING GWA_CJ-BLDAT
 GS_HEADER_BAPI-DOC_DATE.
 PERFORM SUB_DATE_FROMAT_BAPI CHANGING GWA_CJ-BUDAT
 GS_HEADER_BAPI-PSTNG_DATE.
 GS_HEADER_BAPI-REF_DOC_NO = GWA_CJ-XBLNR.
 GS_HEADER_BAPI-ALLOC_NMBR = GWA_CJ-ALLNO.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-KOSTL
 IMPORTING
 OUTPUT = GWA_ITEMS-COSTCENTER.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GWA_CJ-PRCTR
 IMPORTING
 OUTPUT = GWA_ITEMS-PROFIT_CTR.
 APPEND GWA_ITEMS TO GIT_ITEMS.
 CALL FUNCTION 'BAPI_CASHJOURNALDOC_CREATE'
 EXPORTING
 HEADER = GS_HEADER_BAPI
 IMPORTING
 COMPANY_CODE = GS_CJ_KEY-COMP_CODE
 CASH_JOURNAL_NUMBER = GS_CJ_KEY-CAJO_NUMBER
 FISCAL_YEAR = GS_CJ_KEY-FISC_YEAR
 CASH_JOURNAL_DOC_NO = GS_CJ_KEY-POSTING_NUMBER
 TABLES
 ITEMS = GIT_ITEMS
 RETURN = GIT_RETURN.
 IF GIT_RETURN IS NOT INITIAL.
 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_E.
 IF SY-SUBRC <> 0.
 CLEAR GWA_CJ_S.
 MOVE-CORRESPONDING GS_CJ_KEY TO GWA_CJ_S.
 CLEAR GWA_RETURN.
 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_S.
 IF SY-SUBRC = 0.
 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_S-MSG.
 CLEAR GWA_RETURN.
 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_I.
 IF SY-SUBRC = 0.
 CLEAR GWA_CJ_E.
 CONCATENATE GWA_RETURN-MESSAGE GWA_CJ_S-MSG INTO GWA_CJ_E-MSG SEPARATED BY GC_PIPE_FORMAT.
 MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
 GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
 APPEND GWA_CJ_E TO GIT_CJ_E.
 GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
 ELSE.
 IF P_TEST NE GC_X.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 WAIT = LV_WAIT.
 REFRESH:LIT_POSTING ,
 LIT_WTAX_ITEMS ,
 LIT_SPLIT_POSTINGS ,
 LIT_CPD .
 CLEAR: LV_BEG_BALANCE ,
 LV_TOTAL_RECEIPTS ,
 LV_TOTAL_PAYMENTS ,
 LV_TOTAL_CHECKS ,
 LV_RUN_BALANCE ,
 LV_RUN_CASH_BALANCE ,
 LV_NUMB_OF_REC ,
 LV_NUMB_OF_PAYM ,
 LV_NUMB_OF_CHECKS .
 CALL FUNCTION 'FCJ_GET_DATA_FOR_SCREEN'
 EXPORTING
 I_COMP_CODE = GS_CJ_KEY-COMP_CODE
 I_CAJO_NUMBER = GS_CJ_KEY-CAJO_NUMBER
 I_DISPLAY_PERIOD_LO = GS_HEADER_BAPI-PSTNG_DATE
 I_DISPLAY_PERIOD_HI = GS_HEADER_BAPI-PSTNG_DATE
 IMPORTING
 E_BEGINNING_BALANCE = LV_BEG_BALANCE
 E_RUNNING_BALANCE = LV_RUN_BALANCE
 E_RUNNING_CASH_BALANCE = LV_RUN_CASH_BALANCE
 E_TOTAL_RECEIPTS = LV_TOTAL_RECEIPTS
 E_TOTAL_REC_NUMBER = LV_NUMB_OF_REC
 E_TOTAL_PAYMENTS = LV_TOTAL_PAYMENTS
 E_TOTAL_PAYM_NUMBER = LV_NUMB_OF_PAYM
 E_TOTAL_CHECKS = LV_TOTAL_CHECKS
 E_TOTAL_CHECKS_NUMBER = LV_NUMB_OF_CHECKS
 TABLES
 E_POSTINGS = LIT_POSTING
 E_WTAX_ITEMS = LIT_WTAX_ITEMS
 E_SPLIT_POSTINGS = LIT_SPLIT_POSTINGS
 E_CPD = LIT_CPD.
 CALL FUNCTION 'FCJ_POST_ALL'
 EXPORTING
 I_COMP_CODE = GS_CJ_KEY-COMP_CODE
 I_CAJO_NUMBER = GS_CJ_KEY-CAJO_NUMBER
 I_CURRENCY = GS_HEADER_BAPI-CURRENCY
 I_TYP = 'R'
 I_DISPLAY_PERIOD_LO = GS_HEADER_BAPI-PSTNG_DATE
 I_DISPLAY_PERIOD_HI = GS_HEADER_BAPI-PSTNG_DATE
* IMPORTING
* E_ERROR_NUMBER =
 TABLES
 ITCJ_POSTINGS = LIT_POSTING
 ITCJ_WTAX_ITEMS = LIT_WTAX_ITEMS
 ITCJ_SPLIT_POSTINGS = LIT_SPLIT_POSTINGS
 ITCJ_CPD = LIT_CPD
 CHANGING
 P_BEG_BALANCE = LV_BEG_BALANCE
 P_TOTAL_RECEIPTS = LV_TOTAL_RECEIPTS
 P_TOTAL_PAYMENTS = LV_TOTAL_PAYMENTS
 P_TOTAL_CHECKS = LV_TOTAL_CHECKS
 P_RUN_BALANCE = LV_RUN_BALANCE
 P_RUN_CASH_BALANCE = LV_RUN_CASH_BALANCE
 P_NUMB_OF_REC = LV_NUMB_OF_REC
 P_NUMB_OF_PAYM = LV_NUMB_OF_PAYM
 P_NUMB_OF_CHECKS = LV_NUMB_OF_CHECKS.
 COMMIT WORK.
 ENDIF.
 APPEND GWA_CJ_S TO GIT_CJ_S.
 GV_SUCCESS_RECORDS = GV_SUCCESS_RECORDS + GC_1.
 CLEAR GWA_CJ_S.
 ENDIF.
 ENDIF.
 ELSE.
 CLEAR GWA_CJ_E.
 MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
 GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
 APPEND GWA_CJ_E TO GIT_CJ_E.
 GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
 ENDIF.
 ENDIF.
 ELSE.
 GWA_RETURN-MESSAGE = 'Transaction Name does not correspond to any Transaction Number'(017).
 CLEAR GWA_CJ_E.
 MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
 GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
 APPEND GWA_CJ_E TO GIT_CJ_E.
 GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
 ENDIF.
 ENDLOOP.
ENDFORM. " SUB_BAPI_CALL

IDOC or BAPI to use to upload timekeeping and labor schedule to SAP HCM

Similar Messages

Maybe you are looking for