Upload the data into interface

HI Abapers,
My requirement is that i want to upload the data into the transaction where for the header data there are n number of item transactions , so my requirement is to select all the item transactions that should be done in background, so i have written the code below but it is selectiong only the first row
itd2[] = itd[].
*icount = 1.
    LOOP AT itd2 INTO wa_itd2.
icount = 1.
    CONCATENATE 'GWA_MTBAL-CHECK(' icount ')' INTO w_fnam.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                              w_fnam.
      PERFORM bdc_field       USING w_fnam
        'X'.
      icount = icount + 1.
    ENDLOOP.
    PERFORM bdc_dynpro      USING 'SAPMZPP001_PRODORDCONF' '9010'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=GR'.
Pls reply for any changes in code or any clarifications for this post.
Thanks In advance.

Hi thank you for kind reply i need to create the entries for CO Activity /Price planning .
i have to upload data to KP26 which i have posted the fields ..
i already cheked the function modules which you have been given .. it is not suitable ..
Is there any ohter BAPI is there ... le t me know ...
regards
purushotham.ineni

Similar Messages

Problem to upload the data into internal table record length more than 6000

Hi all
I stuck with this problem from past 3 days. I have to upload the data from excel sheet. iam making it tab delimited and trying to upload from gui_upload. but in the structure of file, we have, one field of 4000 characters, and other fields of 255 characters.
how can i upload this into internal table . From excel sheet or from tab delimeted or any other format? or any special function module is there? while iam doing this its truncating the datat 255 characters and not uploading the other fields also...
can any one of you help me out. ASAP
thnks in advance

from one of the forum iam just pasting code which it is used in lsmw, try the same logic in ur code hope it can work.
you have to create multiple lines with do...enddo loop., like this:
(assuming excel_long_text-text is 924 characters long, 7 lines X 132 char)
__GLOBAL_DATA__
data: offset type i,
text_132(132) type c.
__BEGIN_OF_RECORD__ Before Using Conversion Rules
Rule : Default Settings Modified
Code: /sapdmc/ltxtl = init_/sapdmc/ltxtl.
CLEAR offset.
DO 7 TIMES.
text_132 = excel_long_text-text+offset(132).
offset = offset + 132.
__END_OF_RECORD__ After Using Conversion Rules
Rule : Default Settings Modified
Code: transfer_record.
ENDDO.
also check this
COMMIT_TEXT
To load long text into SAP
READ_TEXT
To load long text into SAP

ERROR while uploading the data into ztable with background processing

Hi gurus,
i am trying to upload the data from excel file to internal table
its working fine ..
but........
if i try to upload the data with background processing , in sm37 it is saying "error during the upload of clipboard contents".
Regards,
Sri

Hi,
FM GUI_UPLOAD doesnt work in background, use dataset to upload it from application server.
refer below code
*--Local Variables
DATA : l_file TYPE string,
         l_line TYPE string,
         l_index TYPE sy-tabix.
*--Clear
CLEAR : l_file.
l_file = p_ipfile.
*--Read the data from application server file.
OPEN DATASET l_file FOR INPUT IN TEXT MODE ENCODING DEFAULT.
IF sy-subrc NE 0.
*--Error in opening file
    MESSAGE i368(00) WITH text-005.
ENDIF.
*--Get all the records from the specified location.
DO.
    READ DATASET l_file INTO l_line.
    IF sy-subrc NE 0.
      EXIT.
    ELSE.
      SPLIT l_line AT cl_abap_char_utilities=>horizontal_tab
                      INTO st_ipfile-vbeln
                           st_ipfile-posnr
                           st_ipfile-edatu
                           st_ipfile-wmeng.
      APPEND st_ipfile TO it_ipfile.
    ENDIF.
ENDDO.
Regards,
Prashant

Uploading the Data into BDC using Excel sheet

HI Gurus,
Iam uploading the Data Using Excel sheet.TCode:qp01.
Upto 3 screens the data is passing in a very fine manner.
From the fourth screen I'v to enter the Lineitem for a single material.
Ex: Matnr is PJBRIX.
For this material upto 3 screens the data is same ,but from the line item data,the PJBRIX has 3 characterstics.
How can I upload that data.
Structure:
Matnr Group GroupCounter MicCode Method Lower Upper
Pjbrix     5         6                  zsr001    zsr001   1       15
Pjbrix     5         6                  zsr002     zsr003   4       20
Pjbrix     5         6                  zsr006     zsr0018 2       18
This is the Structure.
Pls gv me the advise or Gv me the code asap.
thanks in advance.

HI Gurus,
Iam uploading the Data Using Excel sheet.TCode:qp01.
Upto 3 screens the data is passing in a very fine manner.
From the fourth screen I'v to enter the Lineitem for a single material.
Ex: Matnr is PJBRIX.
For this material upto 3 screens the data is same ,but from the line item data,the PJBRIX has 3 characterstics.
How can I upload that data.
Structure:
Matnr Group GroupCounter MicCode Method Lower Upper
Pjbrix     5         6                  zsr001    zsr001   1       15
Pjbrix     5         6                  zsr002     zsr003   4       20
Pjbrix     5         6                  zsr006     zsr0018 2       18
This is the Structure.
Pls gv me the advise or Gv me the code asap.
thanks in advance.

How to upload the data into SAP R/3 System

I have a scenario to upload the flat file data into SAP R/3 System.
I will describe my complete scenario here so that it will be better understanding for you to suggest the solution.
The segments that relevant for the upload of customer master data, namely
HD : Header Segment
PF : Partner Function Segment
OP : Output Segment
TX : Tax Segment
CR : Credit Segment
CT : Customer Text Segment

I think you can achieve this with IDOC creation. If it is so follow the steps below.
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Reward Points if useful.

Using bapi how to upload the data into sap database?

hi dear all,
im facing problem with bapi ? let me edcuate on bapi ..
i will be waiting for reply.
my e-id :[email protected]
thanks&regards
shiva.

Hi
A BAPI is a method of a SAP Business Object. BAPI enables SAP and third party applications to interact and integrate
with each other at the Business Object / Process level.
Check this link to know more about BAPI.
http://www.sapgenie.com/abap/bapi/example.htm
http://sappoint.com/abap/
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form
of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The
transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. .
To know more about BDC,
check the link.
http://sappoint.com/abap/
Main differences are...
In case of bdc data transfer takes place from flat file into sap system ie the file existing in sap system to sap sytem
where is bapi's r remotly enabled function modules which are assigned to some business objects n used to transfer the data between different business partners who are using different systems other than sap.
not only that...
when you plan to upgrade your system version then bdc willnot support those upgradations where as bapi's will support.
http://www.sap-img.com/abap/ale-bapi.htm
SAP BAPI
BAPI STEPS
Hope this helps.
ashish

Transaction code used to upload the data in the application server SCM syst

Hi
Could you please anyone tell me the transaction code which has been used to upload the data into the application server in SCM ( APO) system from presentation server.
For ex : R/3 system CG3Y , CG3Z has been used to upload the data into application server similarly way could you please tell me the transaction code is used in the APO system for uploading the data into application server.
Thanks advance for your support.
Regards,
Kiran

try tcode SXDA_TOOLS - copy
(1st you must fill all obligatory fields)
A.

How to uplaod the data into transaction IA01

Hi All,
I have tried to upload the data into transaction IA01 using direct input object 0470.
But one structure for Service Package Overview tab is missing.Can anyone suggest on how we proceed about it,like is there any BAPI to upload the data.Because there are almost 150 fields that need to be uploaded into the transaction which has different tabs in it so it would be very difficult to handle with BDC's.
Thanks and Regards,
Shilpa

Hi All,
I have tried to upload the data into transaction IA01 using direct input object 0470.
But one structure for Service Package Overview tab is missing.Can anyone suggest on how we proceed about it,like is there any BAPI to upload the data.Because there are almost 150 fields that need to be uploaded into the transaction which has different tabs in it so it would be very difficult to handle with BDC's.
Thanks and Regards,
Shilpa

Update the data into the ZTABLE fields thru program logic ..?

hi all,
i have ZTABLE1,ZTABLE2,ZTABLE3, and this tables like ALV grids using object methods.
in the same table fields now i wanted to update the data into the ZTABLE fields thru program logic .
could anyone please help me ....
please provide if anyone of have any program logic that would be helpfull to me.
thanks in advance...
srinivas....

Hi Srinivas,
The following statements are used to upload the data into custom tables.
1. Modify
2. Update
3. Insert
if you are using OO ALV, you should enable the 'SAVE' button in the main toolbar. if the user press the save button, then you should upload the data to the custom table.
please find the example code, in this example 'PERFORM F_SAVE_DATA'(here i gave the message only, you write your own logic here) is used to save the data in custom table.
Report Program: ZB_ALVOOPS_TEST
Line:-----
REPORT ZB_ALVOOPS_TEST MESSAGE-ID ZCR_MESSAGES.
Top Include - Global Data Declaration                        *
INCLUDE ZB_ALVOOPS_TEST_TOP.
SEL Include - Selection Screen                               *
INCLUDE ZB_ALVOOPS_TEST_SEL.
AT SELECTION SCREEN                                          *
Initialization Event                                         *
INITIALIZATION.
Initialize Screen Number.
PERFORM F_INITIALIZE.
Initialize Field Catalog for ALV Grid.
PERFORM F_INITIALIZE_GRID.
END-OF-SELECTION.
Call Display Screen                                          *
CALL SCREEN 9000.
Event Handler - Class Definition and Implementation          *
INCLUDE ZB_ALVOOPS_TEST_CL01.
PBO Event - Module Implementation                            *
INCLUDE ZB_ALVOOPS_TEST_PBO.
PAI Event - Module Implementation                            *
INCLUDE ZB_ALVOOPS_TEST_PAI.
Subroutine Include                                           *
INCLUDE ZB_ALVOOPS_TEST_F01.
Include: ZB_ALVOOPS_TEST_TOP
Line:-------
Type Declaration For Internal Tables                         *
Collection Data
TYPES: BEGIN OF TY_MARA                                                    ,
         MATNR         TYPE MATNR                                         , " Material
         VPSTA         TYPE VPSTA                                         , " Maintenance status of complete material
         MTART         TYPE MTART                                         , " Material Type
         MBRSH         TYPE MBRSH                                         , " Industry Sector
         MATKL         TYPE MATKL                                         , " Material Group
         BISMT         TYPE BISMT                                         , " Old material number
         MEINS         TYPE MEINS                                         , " Base Unit of Measure
         BSTME         TYPE BSTME                                         , " Order unit
         BRGEW         TYPE BRGEW                                         , " Gross weight
         MAKTX         TYPE MAKTX                                         , " Material Description
         ROWCOLOR      TYPE CHAR4                                         , " Row Color
       END OF TY_MARA                                                      .
Flag                                                         *
DATA: FG_REFRESH TYPE XFLD                                               , " Used to Refresh ALV
      FG_SAVE     TYPE XFLD                                               . " Data Saved Or Not.
Internal Table Declaration                                   *
DATA: IT_MARA              TYPE STANDARD TABLE OF TY_MARA                 , " Internal table for Material
      WA_MARA              TYPE TY_MARA                                   . " Workarea for Material
Variable Declaration For General Constants                   *
CONSTANTS: C_SCREEN_SELECT      TYPE SYDYNNR         VALUE '9001'         , " Selection Screen Number
           C_SCREEN_SELECT_NIL TYPE SYDYNNR         VALUE '9002'         , " Empty Screen Number
           C_STATUS9000         TYPE CHAR10          VALUE 'STATUS9000'   , " PF-Status
           C_TITLEBAR           TYPE CHAR4           VALUE '9000'         , " Title Bar
           C_ISSUE_CONTAINER    TYPE SCRFNAME        VALUE 'WORKCONTAINER', " Container Name (Screen Painter)
           C_BUTTON_TYPE        TYPE CHAR1           VALUE '3'            , " Button Type
           C_EXECUTE            TYPE CHAR4           VALUE 'SELE'         , " Functions 'SELE'    -> Execute
           C_BACK               TYPE CHAR4           VALUE 'BACK'         , " Functions 'BACK'    -> Back to main screen
           C_ENTER              TYPE CHAR5           VALUE 'ENTER'        , " Functions 'ENTER'   -> No Action
           C_SEL01              TYPE CHAR5           VALUE 'SEL01'        , " Functions 'SEL01'   -> Toggle Function
           C_SAVE               TYPE CHAR4           VALUE 'SAVE'         , " Functions 'SAVE'    -> Save Function
           C_REFRESH            TYPE CHAR7           VALUE 'REFRESH'      , " Functions 'REFRESH' -> Clear and Fres All objects
           C_ADD_MI             TYPE CHAR6           VALUE 'ADD_MI'       , " Functions 'ADD_MI' -> Add New Media Issue
           C_TRUE               TYPE CHAR1           VALUE 'X'            , " Set X value
           C_REQUIRED           TYPE CHAR1           VALUE '1'            , " Un-Confirmed Qty field obligatory or not.
           C_INPUT              TYPE CHAR1           VALUE '0'            , " Reason field should not be input.
           C_ALV_SAVE           TYPE CHAR1           VALUE 'A'            , " ALV
           C_ERROR              TYPE CHAR1           VALUE 'E'            , " Error Type
           C_SIGN               TYPE CHAR1           VALUE 'I'            , " Sign
           C_OPTION             TYPE CHAR2           VALUE 'EQ'           , " Option.
           C_COMMIT_WAIT        TYPE CHAR1           VALUE '5'            , " Waiting to update in DB
           C_TABNAME            TYPE CHAR1           VALUE '1'            , " Parameter (ALV)
           C_CANCEL             TYPE CHAR1           VALUE 'N'            , " Cancel
           C_YES                TYPE CHAR1           VALUE 'J'            . " Yes.
Variable Declaration For Container and ALV Grid              *
DATA: OBJ_CUST_CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER            , " Container Class
      OBJ_CUST_GRID       TYPE REF TO CL_GUI_ALV_GRID                    . " ALV Grid Class
Field Catalog Declaration For Container and ALV Grid         *
DATA: IT_FIELDCAT TYPE LVC_T_FCAT                                        , " Field Catalog
      IT_EXCLUDE   TYPE UI_FUNCTIONS                                      , " Standard Function Exclude from ALV
      WA_FIELDCAT TYPE LVC_S_FCAT                                        , " For Field Catalog
      WA_LAYOUT    TYPE LVC_S_LAYO                                        . " ALV Layout
Global Variable Declaration                                  *
DATA: OK_CODE                  TYPE SY-UCOMM                              , " OK CODE ( Screen Attribute Don't Change the var.name)
      G_SAVE_CODE              TYPE SY-UCOMM                              , " OK CODE
      G_ANSWER                 TYPE CHAR1                                 , " OK or Cancel.
      G_SELECTION_DYNNR        TYPE SYDYNNR                               , " Screen Number
      G_ERROR_TEXT             TYPE CHAR128                               , " Error Text
      G_SELECTION_TOGGLE_TEXT TYPE CHAR50                                , " Toggle Text, Value: Hide Selection, Show Selection
      G_MATNR                  TYPE MATNR                                 , " Material
      G_SMATNR                 TYPE MATNR                                 , " Material
      G_SMTART                 TYPE MTART                                 . " Material Type
Include: ZB_ALVOOPS_TEST_SEL
Line:-------
Selection Screen
SELECTION-SCREEN BEGIN OF SCREEN 9001 AS SUBSCREEN                           .
SELECTION-SCREEN BEGIN OF BLOCK SELECTION WITH FRAME TITLE TEXT-001          .
SELECT-OPTIONS: S_MATNR FOR G_SMATNR                                        , " Material
                S_MTART FOR G_SMTART                                        . " Material Type
SELECTION-SCREEN   END OF BLOCK SELECTION                                    .
SELECTION-SCREEN   END OF SCREEN 9001                                        .
Empty Selection
SELECTION-SCREEN BEGIN OF SCREEN 9002 AS SUBSCREEN                           .
SELECTION-SCREEN BEGIN OF BLOCK SELECTION_NIL WITH FRAME TITLE TEXT-002      .
Nil
SELECTION-SCREEN   END OF BLOCK SELECTION_NIL                                .
SELECTION-SCREEN   END OF SCREEN 9002                                        .
Include: ZB_ALVOOPS_TEST_CL01
Line:-------
CLASS lcl_event_handler DEFINITION                                  *
Event Handler Class Definition                                      *
CLASS LCL_EVENT_HANDLER DEFINITION.
PUBLIC SECTION.
    METHODS:
    HANDLER_TOOLBAR      FOR EVENT TOOLBAR OF CL_GUI_ALV_GRID
                             IMPORTING E_OBJECT E_INTERACTIVE     ,
    HANDLER_USER_COMMAND FOR EVENT USER_COMMAND OF CL_GUI_ALV_GRID
                             IMPORTING E_UCOMM                     .
ENDCLASS.                    "lcl_event_handler DEFINITION
CLASS lcl_event_handler IMPLEMENTATION                              *
Event Class Implementation.                                         *
CLASS LCL_EVENT_HANDLER IMPLEMENTATION.
Toolbar -----Create 'Add Issue' button
METHOD HANDLER_TOOLBAR.
    DATA: L_WA_TOOLBAR TYPE STB_BUTTON.                                          " Toolbar
    CLEAR: L_WA_TOOLBAR.
Button Type
    L_WA_TOOLBAR-BUTN_TYPE = C_BUTTON_TYPE   .            " 3.
    APPEND L_WA_TOOLBAR TO E_OBJECT->MT_TOOLBAR.
Add Issue Button.
    CLEAR: L_WA_TOOLBAR.
    L_WA_TOOLBAR-FUNCTION   = 'ADD_MI'   .                                         " 'ADD_MI'   .
    L_WA_TOOLBAR-ICON       = 'ICON_CREATE'.
    L_WA_TOOLBAR-QUICKINFO = 'CREATE'   .                                         " 'Add Issue'.
    L_WA_TOOLBAR-TEXT       = 'CREATE'   .                                         " 'Add Issue'.
    L_WA_TOOLBAR-DISABLED   = ''.
    APPEND L_WA_TOOLBAR TO E_OBJECT->MT_TOOLBAR.
    CLEAR: L_WA_TOOLBAR.
ENDMETHOD.                    "handler_toolbar
User Actions Events-- Handle 'Add Issue' Button Click.
METHOD HANDLER_USER_COMMAND.
    CASE E_UCOMM.
Add Issue Button.
      WHEN C_ADD_MI.
        IF NOT G_MATNR IS INITIAL.
          FG_REFRESH = C_TRUE.
          PERFORM F_ADD_MEDIAISSUE.
        ENDIF.
    ENDCASE.
Refresh Control
    CALL METHOD CL_GUI_CFW=>FLUSH
      EXCEPTIONS
        CNTL_SYSTEM_ERROR = 1
        CNTL_ERROR        = 2
        OTHERS            = 3.
Handle Exceptions
    IF SY-SUBRC <> 0.
      CASE SY-SUBRC.
        WHEN 1.
          G_ERROR_TEXT = TEXT-026.                                        " 'Control System Error'.
        WHEN 2.
          G_ERROR_TEXT = TEXT-027.                                        " 'Control CL_GUI_CFW Has Raised Error'.
      ENDCASE.
        MESSAGE G_ERROR_TEXT TYPE 'E'.
    ENDIF.
Refresh Alv Grid.
    PERFORM F_REFRESH_GRID.
ENDMETHOD.                    "handler_user_command
ENDCLASS.                    "lcl_event_handler IMPLEMENTATION
Object Ref. Event Class.
DATA: OBJ_EVENT_HANDLER TYPE REF TO LCL_EVENT_HANDLER.
Include: ZB_ALVOOPS_TEST_PBO
Line:----
Module STATUS_9000 OUTPUT                                        *
Set PF-Status                                                      *
MODULE STATUS_9000 OUTPUT.
PF Status
SET PF-STATUS C_STATUS9000 .
SET TITLEBAR C_TITLEBAR    .
ENDMODULE.                 " STATUS_9000 OUTPUT
Module Create_Alvgrid OUTPUT                                     *
Create Or Refresh ALV Grid                                         *
MODULE CREATE_ALVGRID OUTPUT.
PERFORM F_PROCESS_ALV .
PERFORM F_REFRESH_GRID.
ENDMODULE.                 " create_alvgrid OUTPUT
Include: ZB_ALVOOPS_TEST_PAI
Line:----
Module exit_command INPUT                                        *
Exit Command ( Cancel and Exit )                                   *
MODULE EXIT_COMMAND INPUT.
LEAVE PROGRAM.
ENDMODULE.                 " exit_command INPUT
Module user_command_9000 INPUT                                   *
User Command - Process toolbar Events                              *
MODULE USER_COMMAND_9000 INPUT.
Take an Action based on user Input
G_SAVE_CODE = OK_CODE.
CLEAR OK_CODE.
CASE G_SAVE_CODE.
Back
    WHEN C_BACK .
Raise the Confirmation Message When User not saved the data.
      IF FG_SAVE = C_YES.
        PERFORM F_EXITCHECK CHANGING G_ANSWER .
        IF G_ANSWER = C_YES.
          PERFORM F_SAVE_DATA.
        ELSE.
          CLEAR G_SAVE_CODE.
        ENDIF.
        CLEAR: FG_SAVE.
      ENDIF.
      LEAVE PROGRAM.
Enter
    WHEN C_ENTER.
Execute ( F8 )
    WHEN C_EXECUTE .
      IF IT_MARA IS INITIAL.
        PERFORM F_SELECTMATERIAL.
      ENDIF.
Toggle Button
    WHEN C_SEL01.
      PERFORM F_TOGGLE_SELECTION_SCREEN.                                  " USING ok_code.
SAVE ( CTRL+S )
    WHEN C_SAVE.
      IF NOT G_MATNR IS INITIAL.
        PERFORM F_SAVE_DATA.
        CLEAR: G_MATNR.
      ENDIF.
New Entry ( CTRL+F1 )
    WHEN C_REFRESH.
      PERFORM F_REFRESH_DATA.
ENDCASE.
ENDMODULE.                 " user_command_9000 INPUT
Include: ZB_ALVOOPS_TEST_F01
Line:----
Form f_toggle_selection_screen                                    *
Toggle Function - Hide Selection / Show Selection                  *
FORM F_TOGGLE_SELECTION_SCREEN.
Toggle Function
IF G_SELECTION_DYNNR = C_SCREEN_SELECT.
    G_SELECTION_DYNNR = C_SCREEN_SELECT_NIL.
    G_SELECTION_TOGGLE_TEXT = TEXT-902.
ELSE.
    G_SELECTION_DYNNR = C_SCREEN_SELECT.
    G_SELECTION_TOGGLE_TEXT = TEXT-901.
ENDIF.
ENDFORM.                    " f_toggle_selection_screen
Form f_initialize
Initialize Screen Number and Text
FORM F_INITIALIZE .
Initialize Screen Number
G_SELECTION_DYNNR      = C_SCREEN_SELECT.
G_SELECTION_TOGGLE_TEXT = TEXT-901.
ENDFORM.                    "f_initialize
Form f_selectmaterial                                           *
FORM F_SELECTMATERIAL .
Select the data from Mara Table
SELECT A~MATNR
         A~VPSTA
         A~MTART
         A~MBRSH
         A~MATKL
         A~BISMT
         A~MEINS
         A~BSTME
         A~BRGEW
         B~MAKTX
    INTO TABLE IT_MARA
    FROM MARA AS A INNER JOIN MAKT AS B ON AMATNR = BMATNR
   WHERE A~MATNR IN S_MATNR
     AND A~MTART IN S_MTART
     AND B~SPRAS = 'EN'.
IF SY-SUBRC = 0.
    FG_REFRESH = C_TRUE.
    FG_SAVE     = C_YES .
    G_MATNR     = C_TRUE.
    LOOP AT IT_MARA INTO WA_MARA WHERE BRGEW >= 200.
      WA_MARA-ROWCOLOR = 'C310'.
      MODIFY IT_MARA FROM WA_MARA.
    ENDLOOP.
ELSE.
    MESSAGE 'No data Found' TYPE 'E'.
ENDIF.
ENDFORM.                    " f_selectmaterial
Form f_initialize_grid                                            *
Initialize Field Catalog.                                          *
FORM F_INITIALIZE_GRID .
field catalog
PERFORM F_ATTRFCAT USING :
                   'MATNR' '1' '0'   TEXT-005       '15' '0' 'X' ' ' ' ',
                   'VPSTA' '1' '1'   TEXT-006       '15' '0' 'X' ' ' ' ',
                   'MTART' '1' '2'   TEXT-007       '15' '0' ' ' ' ' ' ',
                   'MBRSH' '1' '3'   TEXT-008       '15' '0' ' ' ' ' ' ',
                   'MATKL' '1' '4'   TEXT-009       '15' '0' ' ' 'X' ' ',
                   'BISMT' '1' '5'   TEXT-010       '15' '0' ' ' ' ' ' ',
                   'MEINS' '1' '6'   TEXT-011       '15' '0' ' ' ' ' ' ',
                   'BSTME' '1' '7'   TEXT-012       '15' '0' ' ' ' ' ' ',
                   'MAKTX' '1' '8'   TEXT-013       '15' '0' ' ' ' ' 'C711',
                   'BRGEW' '1' '9'   TEXT-014       '15' '0' ' ' ' ' ' '.
Set Editable Fields in ALV.
PERFORM F_SETEDIT_FIELDS CHANGING IT_FIELDCAT.
ENDFORM.                    "f_initialize_grid
Form f_setedit_fields                                             *
Set Editable Fields in ALV                                         *
C_IT_FIELDCAT <-- Field Catalog                                  *
FORM F_SETEDIT_FIELDS CHANGING C_IT_FIELDCAT TYPE LVC_T_FCAT.
Local Variable Declaration.
DATA: LS_FIELDCAT LIKE LINE OF C_IT_FIELDCAT.                           " Field Catalog
Create Editable Fields.
LOOP AT C_IT_FIELDCAT INTO LS_FIELDCAT.
    CASE LS_FIELDCAT-FIELDNAME.
      WHEN 'BRGEW'.
        LS_FIELDCAT-EDIT = C_TRUE.
      WHEN 'MAKTX'.
        LS_FIELDCAT-EDIT = C_TRUE.
    ENDCASE.
    MODIFY C_IT_FIELDCAT FROM LS_FIELDCAT.
ENDLOOP.
ENDFORM.                    " f_setedit_fields
Form f_attrfcat                                                   *
Update Field Catalog Internal Table                                *
U_FIELDNAME     --> Field Name                                    *
U_ROW_POS       --> Row Position                                  *
U_COL_POS       --> Column Position                               *
U_SELTEXT_L     --> Display Column Heading                        *
U_OUTPUTLEN     --> Heading Output Length                         *
U_DECIMALS_OUT --> Number of decimal places in output            *
U_KEY           --> Key in ALV Display                            *
U_FIX           --> Existence of fixed values                     *
FORM F_ATTRFCAT USING
                    U_FIELDNAME    TYPE SLIS_FIELDNAME
                    U_ROW_POS      TYPE SYCUROW
                    U_COL_POS      TYPE SYCUCOL
                    U_SELTEXT_L    TYPE SCRTEXT_L
                    U_OUTPUTLEN    TYPE OUTPUTLEN
                    U_DECIMALS_OUT TYPE CHAR1
                    U_KEY          TYPE CHAR1
                    U_FIX          TYPE VALEXI
                    U_COL_COLOR    TYPE LVC_EMPHSZ.
Update field catalog.
WA_FIELDCAT-FIELDNAME    = U_FIELDNAME.
WA_FIELDCAT-ROW_POS      = U_ROW_POS.
WA_FIELDCAT-COL_POS      = U_COL_POS.
WA_FIELDCAT-COLTEXT      = U_SELTEXT_L.
WA_FIELDCAT-SELTEXT      = U_SELTEXT_L.
WA_FIELDCAT-OUTPUTLEN    = U_OUTPUTLEN.
WA_FIELDCAT-DECIMALS_O   = U_DECIMALS_OUT.
WA_FIELDCAT-KEY          = U_KEY.
WA_FIELDCAT-VALEXI       = U_FIX.
WA_FIELDCAT-EMPHASIZE    = U_COL_COLOR.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
ENDFORM.                    "ATTR_FCAT
Form f_refresh_data                                               *
Clear All the objects used in the program ( Data Related )         *
FORM F_REFRESH_DATA .
Clear All the Objects Used in Our Program.
CLEAR: S_MATNR      ,
         S_MTART      ,
         IT_MARA      ,
         OK_CODE      ,
         FG_REFRESH   ,
         FG_SAVE      ,
         G_SAVE_CODE ,
         G_MATNR      .
FREE: S_MATNR      ,
         S_MTART      ,
         IT_MARA      ,
         OK_CODE      ,
         FG_REFRESH   ,
         FG_SAVE      ,
         G_SAVE_CODE ,
         G_MATNR      .
Refresh Alv.
FG_REFRESH = C_TRUE.
ENDFORM.                    " f_refresh_data
Form f_process_alv                                                *
1. Create Custom Container                                         *
2. Create ALV Grid                                                 *
3. Exclude Standard Functions                                      *
4. Display the ALV                                                 *
5. Register the Events.                                            *
FORM F_PROCESS_ALV .
Display ALV
Custom Container
IF OBJ_CUST_CONTAINER IS INITIAL.
    CREATE OBJECT OBJ_CUST_CONTAINER
      EXPORTING
        CONTAINER_NAME = C_ISSUE_CONTAINER.
ALV Grid
    IF OBJ_CUST_GRID IS INITIAL.
      CREATE OBJECT OBJ_CUST_GRID
        EXPORTING
          I_PARENT = OBJ_CUST_CONTAINER.
    ENDIF.
Exclude Standard Functions
    PERFORM F_EXCLUDETOOLBAR USING OBJ_CUST_GRID
                          CHANGING IT_EXCLUDE.
Layout.
    WA_LAYOUT-CWIDTH_OPT = C_TRUE.
    WA_LAYOUT-INFO_FNAME = 'ROWCOLOR'.
ALV Grid Display
    CALL METHOD OBJ_CUST_GRID->SET_TABLE_FOR_FIRST_DISPLAY
      EXPORTING
       IS_LAYOUT            = WA_LAYOUT
        IT_TOOLBAR_EXCLUDING = IT_EXCLUDE
        I_SAVE               = C_ALV_SAVE
      CHANGING
        IT_FIELDCATALOG      = IT_FIELDCAT[]
        IT_OUTTAB            = IT_MARA.
ENDIF.
Register Editable ALV Events
CALL METHOD OBJ_CUST_GRID->REGISTER_EDIT_EVENT
    EXPORTING
      I_EVENT_ID = CL_GUI_ALV_GRID=>MC_EVT_MODIFIED
    EXCEPTIONS
      ERROR      = 1
      OTHERS     = 2.
*Create Object for Custom Event Handler Class if the ref. object is
*initial.
IF OBJ_EVENT_HANDLER IS INITIAL.
    CREATE OBJECT OBJ_EVENT_HANDLER.
ENDIF.
Register Events
SET HANDLER: OBJ_EVENT_HANDLER->HANDLER_TOOLBAR       FOR
OBJ_CUST_GRID,
               OBJ_EVENT_HANDLER->HANDLER_USER_COMMAND FOR
               OBJ_CUST_GRID.
Set Toolbar
CALL METHOD OBJ_CUST_GRID->SET_TOOLBAR_INTERACTIVE.
ENDFORM.                    " f_process_alv
Form f_excludetoolbar                                             *
Exclude Standard Functions from ALV                                *
U_OBJ_CUST_GRID --> Instant for CL_GUI_ALV_GRID                  *
C_IT_EXCLUDE     <-- Internal table for Exclude                   *
FORM F_EXCLUDETOOLBAR USING U_OBJ_CUST_GRID TYPE REF TO CL_GUI_ALV_GRID
                    CHANGING C_IT_EXCLUDE     TYPE UI_FUNCTIONS.
Exclude Standard Functions
CLEAR: C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_CHECK              TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_REFRESH            TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_COPY           TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_COPY_ROW       TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_CUT            TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_DELETE_ROW     TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_APPEND_ROW     TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_INSERT_ROW     TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_MOVE_ROW       TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_PASTE          TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_PASTE_NEW_ROW TO C_IT_EXCLUDE.
APPEND U_OBJ_CUST_GRID->MC_FC_LOC_UNDO           TO C_IT_EXCLUDE.
ENDFORM.                    " f_excludetoolbar
Form f_create_returnrequest                                       *
Create Return Request based on the Work container ( ALV Grid Data) *
FORM F_CREATE_RETURNREQUEST.
Message to save
ENDFORM.                    " f_create_returnrequest
Form f_add_mediaissue                                             *
Create New Media Issue if the user click 'ADD ISSUE' Button.       *
1. Get the Input From User                                         *
2. Get Total Delivery and Return Quantity                          *
3. Append to Final internal table                                  *
FORM F_ADD_MEDIAISSUE .
Local Variable Declaration.
MESSAGE 'Add Button Clicked' TYPE 'I'.
ENDFORM.                    " f_add_mediaissue
Form f_refresh_grid                                               *
Refresh ALV Grid                                                   *
FORM F_REFRESH_GRID .
Refresh ALV Grid.
IF FG_REFRESH IS NOT INITIAL.
    CALL METHOD OBJ_CUST_GRID->REFRESH_TABLE_DISPLAY.
    CLEAR: FG_REFRESH.
ENDIF.
ENDFORM.                    " f_refresh_grid
Form f_getcollectissue                                            *
FORM F_GETCOLLECTISSUE .
Collection Plan Data
ENDFORM.                    " f_getcollectissue
Form f_perpare_final                                              *
FORM F_PERPARE_FINAL .
Perpare Final Internal table
ENDFORM.                    " f_perpare_final
Form f_validate_data                                              *
FORM F_VALIDATE_DATA.
Message if any data validation.
ENDFORM.                    " f_validate_data
Form f_modify_final                                               *
Update Actual Delivery Qty and Return Qty in Final Internal table *
Form f_save_data                                                  *
Save the Data When User Click 'Save' Button                        *
FORM F_SAVE_DATA .
Message
MESSAGE 'Save Button Clicked' TYPE 'I'.
ENDFORM.                    "f_save_data
Form f_exitcheck                                                  *
When User Exit from the Transaction then Raise Confirmation message*
C_ANSWER <-- OK or Cancel.                                       *
FORM F_EXITCHECK CHANGING C_ANSWER TYPE CHAR1.
Security Check.
C_ANSWER = C_CANCEL.
CALL FUNCTION 'POPUP_TO_CONFIRM_DATA_LOSS'
    EXPORTING
      TITEL = TEXT-039
    IMPORTING
      ANSWER = C_ANSWER.
ENDFORM.                    "f_exitcheck
Screen Numer : 9000
Line:------
PROCESS BEFORE OUTPUT.
MODULE STATUS_9000.
CALL SUBSCREEN: SELECTIONSCREEN INCLUDING SY-CPROG G_SELECTION_DYNNR.
MODULE CREATE_ALVGRID.
PROCESS AFTER INPUT.
MODULE EXIT_COMMAND AT EXIT-COMMAND.
CALL SUBSCREEN: SELECTIONSCREEN.
MODULE USER_COMMAND_9000.
pls reward if it is useful

Custom PL/SQL API that inserts the data into a custom interface table.

We are developing a custom Web ADI integrator for importing suppliers into Oracle.
The Web ADI interface is a custom PL/SQL API that inserts the data into a custom interface table. We have defined the content, uploader and an importer. The importer is again a custom PL/SQL API that will process the records inserted into the custom table and updates the STATUS column of the custom interface table. We want to show the status column back on the spreadsheet.
Defined the 'Document Row' import rule and added the rows that would identify the unique record.
Errored row import rule, we are using a SELECT * from custom_table where status<>'Success' and vendor_name=$param$.vendor_name
The source of this parameter is import.vendor_name
We have also defined an Error lookup.
After the above setup is completed, we invoke the create document and click on Oracle->Upload.
The records are getting imported, but the importer program is failing with An error has occurred while running an API import. The ERRORED_ROWS step 20003:ER_500141, parameter number 1 must contain the value BIND in attribute 1.'

The same issue.
Need help.
Also checked bne.log, no additional information.
<bne:document xmlns:bne="http://www.oracle.com/bne">
<bne:message bne:type="DATA" bne:text="BNE_VALID_ROW_COUNT" bne:value="11" />
<bne:message bne:type="DATA" bne:text="BNE_INVALID_ROW_COUNT" bne:value="0" />
<bne:message bne:type="ERROR" bne:text="An error has occurred while running an API import"
bne:cause="The ERRORED_ROWS step 20003:ER_500165, parameter number 1 must contain the value BIND in attribute 1."
bne:action="" bne:source="BneAPIImporter" >
<bne:context bne:collection="collection_1" />
</bne:message><bne:message bne:type="STATUS"
bne:text="No rows uploaded" bne:value="" >
<bne:context bne:collection="collection_1" /></bne:message>
<bne:message bne:type="STATUS" bne:text="0 rows were invalid" bne:value="" >
<bne:context bne:collection="collection_1" /></bne:message></bne:document>

How to upload the data from two sheets in one excel into SAP

Hi experts,
                My requirement is to upload the data from two sheets in an excel into an internal table.How can this be achieved.Is some OLE application has to be used?
Thanks
Abhishek

Hi
see this program will upload excel file to application.
*& Report ZSD_EXCEL2
REPORT ZSD_EXCEL2.
types: begin of ttab ,
      fld1(30) type c,
      fld2(30) type c,
      fld3(30) type c,
      fld4(30) type c,
      fld5(30) type c,
      end of ttab.
data: itab type table of ttab with header line.
selection-screen skip 1.
parameters: p_file type localfile default
            'C:\test.xls'.
selection-screen skip 1.
at selection-screen on value-request for p_file.
call function 'KD_GET_FILENAME_ON_F4'
       exporting
            static    = 'X'
       changing
            file_name = p_file.
start-of-selection.
clear itab. refresh itab.
perform upload_data.
loop at itab.
    write:/ itab-fld1, itab-fld2, itab-fld3, itab-fld4, itab-fld5.
endloop.
* Upload_Data
form upload_data.
data: file type rlgrap-filename.
data: xcel type table of alsmex_tabline with header line.
file = p_file.
call function 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       exporting
            filename                = file
            i_begin_col             = '1'
            i_begin_row             = '1'
            i_end_col               = '200'
            i_end_row               = '5000'
       tables
            intern                  = xcel
       exceptions
            inconsistent_parameters = 1
            upload_ole              = 2
            others                  = 3.
loop at xcel.
    case xcel-col.
      when '0001'.
        itab-fld1 = xcel-value.
      when '0002'.
        itab-fld2 = xcel-value.
      when '0003'.
        itab-fld3 = xcel-value.
      when '0004'.
        itab-fld4 = xcel-value.
      when '0005'.
        itab-fld5 = xcel-value.
    endcase.
    at end of row.
      append itab.
      clear itab.
    endat.
endloop.
endform.

Uploading the data from a flat file into ztable

Hi,
I have a requirement where I have to upload the data from 2 flat files into 2 z tables(ZRB_HDR,ZRB_ITM).From the 1st flat file only data for few fields have to be uploaded into ztable(ZRB_HRD) .Fromthe 2nd flat file data for all the fields have to me uploaded into ztable(ZRB_ITM). How can I do this?
Regards,
Hema

hi,
declare two internal table with structur of your tables.
your flat files should be .txt files.
now make use of GUI_UPLOAD function module to upload your flatfile into internal tables.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename            = 'c:\file1.txt'
      has_field_separator = 'X'
    TABLES
      data_tab            = itab1
    EXCEPTIONS
      OTHERS              = 1.
use this function twice for two tables.
then loop them individually and make use of insert command.

Interface to transfer the data into payroll

hi folks,
I need to transfer the time data entry found in CATSDB intp payroll. what is the interface or BAPI FM that I can use?
Also , I need a clarification - is the data stored in CATSDB table - the final time data of the employees ?
Thanks
Vinu

Hi Vinu,
You can use the function module BAPI_CATIMESHEETMGR_INSERT for inserting the data into CATSDB table. (Transaction CAT2).
The function module BAPI_CATIMESHEETRECORD_GETLIST is used to read the data from CATSDB.
The function module BAPI_CATIMESHEETMGR_CHANGE is used to change the existing records.
Please close the issue with points(appreciate) if it helps.
Good luck.
Venu

Can anyone confirm the date used for pushing the data into AR interface table? Is it abse don Actual ship date or scheduled ship date?

Can anyone confirm the date used for pushing the data into AR interface table? Is it abse don Actual ship date or scheduled ship date? We are facing a scenario where trx date is lower than the actual ship to which logically sounds incorrect.
Appreciate any quick response around this.

Hi,
Transaction date will be your autoinvoice master program submission level date (If you haven't setup any logic.
Please check the program level default date, if user enter old date ststem will pick the same.
Customer is trying to set the value of the profile OM:Set receivables transaction date as current date for non-shippable lines at the responsiblity level. System does not set the transaction date to current date in ra_interface_lines_all.
CAUSE
Customer has used the functionality in R11i. But after the upgrade to R12, the system functions differently than R11i.
SOLUTION
1.Ensure that there are no scheduled workflow background process run.
2.Set the profile "OM: Set Receivables Transaction Date as Current Date for Non-Shippable Lines" at Responsibility level only as Yes.
3.Now switch the responsibility to which the profile is set.
4.Create order for Non-Shippable Lines and progress it to invoicing.
5.Ensure that the 'workflow background process' concurrent program is run in the same responsibility and this line is considered in it.
6.Now check if the 'SHIP_DATE_ACTUAL' is populated to ra_interface_lines_all

" Can not interpret the data in file " error while uploading the data in DB

Dear All ,
After running the below report I am getting the " Can not interpret the data in file " error.
Need to upload the data in DB through excel or .txt file.
Kindly advise to resolve the issue.
REPORT ZTEST_4.
data : it like ZPRINT_LOC occurs 0 with header line,
FILETABLE type table of FILE_TABLE,
wa_filetable like line of filetable,
wa_filename type string,
rc type i.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
CHANGING
FILE_TABLE = filetable
RC = rc.
IF SY-SUBRC = 0.
read table filetable into wa_filetable index 1.
move wa_filetable-FILENAME to wa_filename.
Else.
Write: / 'HI'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
start-of-selection.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = wa_filename
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
TABLES
DATA_TAB = it.
IF SY-SUBRC = 0.
Write: / 'HI'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
insert ZPRINT_LOC from table it.
if sy-subrc = 0.
commit work.
else.
rollback work.
endif.
Regards
Machindra Patade
Edited by: Machindra Patade on Apr 9, 2010 1:34 PM

Dear dedeepya reddy,
Not able to upload the excel but have sucess to upload the .csv file to db through the below code. Thanks for your advise.
REPORT ZTEST_3.
         internal table declaration
DATA: itab TYPE STANDARD TABLE OF ZPRINT_LOC,
      wa LIKE LINE OF itab,
      wa1 like line of itab.
                   variable declaration
DATA: v_excel_string(2000) TYPE c,
       v_file LIKE v_excel_string VALUE    'C:\Documents and Settings\devadm\Desktop\test.csv', " name of the file
        delimiter TYPE c VALUE ' '.         " delimiter with default value space
     read the file from the application server
OPEN DATASET v_file FOR INPUT IN TEXT MODE ENCODING DEFAULT.
IF sy-subrc NE 0.
write:/ 'error opening file'.
ELSE.
    WHILE ( sy-subrc EQ 0 ).
      READ DATASET v_file INTO wa.
      IF NOT wa IS INITIAL.
        append wa TO itab.
      ENDIF.
      CLEAR wa.
    ENDWHILE.
ENDIF.
CLOSE DATASET v_file.
EXEC SQL.
     TRUNCATE TABLE "ZPRINT_LOC"
ENDEXEC.
*------display the data from the internal table
LOOP AT itab into wa1.
WRITE:/ wa1-mandt,wa1-zloc_code,wa1-zloc_desc,wa1-zloc,wa1-zstate.
ENDLOOP.
insert ZPRINT_LOC from table itab.

Upload the data into interface

Similar Messages

Maybe you are looking for