Program to Find Customer Details

Hi,
I have a specific requirement that all customer relevant data should be downloaded into flat files.
For example, let us take customer, we need complete information of a customer in a single table so that we can export the same to flat file.
RMDATAGEN this program is for Material. here i get all Material details. simillarly can i get all for Customer.
Please advise if there are any programs available.
Thanks in advance
Thanks,

Hi
you can use BAPIs- BAPI_CUSTOMER_GETDETAIL2 and BAPI_CUSTOMER_GETDETAIL1 to get the customer details.
Regards
Geeta Gupta

Similar Messages

Program to find Custom objects

Hi everyone,
As per the requirement, I need to build a program which will list down all custom objects (tables, data element, domain, function module & etc) in a given program.
Could you please tell which is optimized way to write the program and which are the tables/function modules I need to use.
Thanks in advance.
Regards,
Balaji Viswanath.

hi ,
you can find lots of program here
http://www.guidancetech.com/people/holland/sap/abap/
Program to list all sap tables
REPORT ZZBGS044 MESSAGE-ID Z1 LINE-COUNT 65 LINE-SIZE 132
                NO STANDARD PAGE HEADING.
Description: This program list all tables in        regards to the   *
             selection criteria.                                     *
Customizing: You need not to make any customizing to use this program*
Change of    You only have to check that tables, functions and       *
release:     includes till exists. Bedst just to check and run the   *
             program.                                                *
Programmer: Benny G. Sørensen                                       *
Date:        July 1995                                               *
SAP R/3      2.2F                                                    *
Corrections----
Date        Userid     Correction                                    *
xx-xx-xxxx xxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx *
TABLES: DD02V                "SAP tables view
DATA: BEGIN OF DYNTAB OCCURS 2000.
        INCLUDE STRUCTURE BDCDATA.
DATA: END OF DYNTAB.
DATA: BEGIN OF TABLES OCCURS 100.
        INCLUDE STRUCTURE DD02V.
DATA: END OF TABLES.
DATA: L        TYPE I,
      REPL(30) TYPE C VALUE '????????????????????????????'.
FIELD-SYMBOLS:
PARAMETERS:
TABLE(30) TYPE C,
TITLE(74) TYPE C LOWER CASE DEFAULT ' ',
DOWNLOAD(1) TYPE C DEFAULT ' ',
FILENAME(65) TYPE C DEFAULT 'c:SAPDOC?',
EXCEPT(30) TYPE C DEFAULT ' '.
START-OF-SELECTION.
IF TABLE = ''.
TABLE = '*' .
ENDIF.
IF TITLE = ''.
TITLE = '*' .
ENDIF.
TRANSLATE TABLE USING '*%'.
TRANSLATE TITLE USING '*%'.
CONDENSE EXCEPT NO-GAPS.
L = STRLEN( EXCEPT ).
IF L > 0.
ASSIGN REPL(L) TO
ENDIF.
SELECT * FROM DD02V INTO TABLES
WHERE DDLANGUAGE = SY-LANGU
AND TABNAME LIKE TABLE
AND DDTEXT LIKE TITLE.
HIDE DD02V-TABNAME.
IF EXCEPT NE ''.
REPLACE EXCEPT LENGTH L WITH
INTO TABLES-TABNAME.
ENDIF.
TRANSLATE TABLE USING '% '.
CONDENSE TABLE NO-GAPS.
IF TABLES-TABNAME CS TABLE.
WRITE:/ TABLES-TABNAME, ' ', TABLES-DDTEXT.
APPEND TABLES.
ENDIF.
ENDSELECT.
IF DOWNLOAD NE ''.
CALL FUNCTION 'WS_DOWNLOAD'
EXPORTING
FILENAME = FILENAME
FILETYPE = 'WK1' "ASC, WK1, DBF, DAT, bin
TABLES
DATA_TAB = TABLES.
ENDIF.
AT LINE-SELECTION.
SET PARAMETER ID 'DOB' FIELD SY-LISEL(30) .
CALL TRANSACTION 'SE12' AND SKIP FIRST SCREEN.
AT PF8.
CHECK SY-LISEL <>
SET PARAMETER ID 'DTB' FIELD SY-LISEL(10) .
REFRESH DYNTAB.
PERFORM DYNPRO USING:
     'X' 'SAPMSTAZ'     '0100'        "Selection screen
    ,' ' 'DD02V-TABNAME' SY-LISEL(10).
CALL TRANSACTION 'SE16' USING DYNTAB MODE 'A' .
FORM DYNPRO USING DYNBEGIN NAME VALUE.
IF DYNBEGIN = 'X'.
    CLEAR DYNTAB.
    MOVE : NAME TO DYNTAB-PROGRAM,
            VALUE TO DYNTAB-DYNPRO,
            DYNBEGIN TO DYNTAB-DYNBEGIN.
    APPEND DYNTAB.
ELSE.
    CLEAR DYNTAB.
    MOVE: NAME TO DYNTAB-FNAM,
           VALUE TO DYNTAB-FVAL.
    APPEND DYNTAB.
ENDIF.
ENDFORM.
Yogesh N

How to find out which program fill a custom table ?

Dear All,
I am trying to find out which program fill custom table, I tried se11, which programs used this custom table via where used list but could not find. Is there any different way ?
Regards

Hi Sappcon,
yes, it is as Brad said, but you should extend the approach regarding this tables content: If it is related to an existing business object (i.e. order, delivery or the like), you may have a look at user exits/Badis in that field.
Also, the dynamic approach is possible. First use report RPR_ABAP_SOURCE_SCAN to find the name of the table in all programs in customer name space - it may be defined as a constant in program/function group/class.
If the dynamic approach is used, the name of the table may be determined by reading another (custom) table or even in a programs text pool. You may find this by searching a pattern UPDATE() - or MODIFY/INSERT in customer programs.
If the table has update date/time fields, check what jobs or online activities can be responsible.
If, after all, you still do not know, then I'd say this is a consulting issue
Regards,
Clemens

Autoinvoice Master Program is not populating Paying Customer Details

Hi All,
We have requirement to populate paying customer details in AR Transactions form.
We were able to load data into interface tables(Paying_customer_id) and Autoinvoice Master Program is running successfully without any errors/warnings,but Paying customer information is not going to base tables.
Can any one please advise on this?

Hello.
See MOS DOC ID 1097660.1
Octavio

How to find CUSTOMER EXIT for a Standard SAP program

How to find CUSTOMER EXIT for a Standard SAP program

Hi
To introduce the techniques of enhancement in standard SAP system. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
They do not affect standard SAP source code.
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates.
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System.
Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).
You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
SAP application programmers create SAP enhancements in transaction SMOD using function module exits, menu exits, and screen exits.
Customers are given a catalog containing an overview of existing SAP enhancements. They can then combine the SAP enhancements they want into an enhancement project using transaction CMOD.
SAP enhancements are made up of component parts. These components include function module exits, menu exits, and screen exits. A specific component may be used only once in a single SAP enhancement (this guarantees the uniqueness of SAP enhancements).
Customer enhancement projects consist of SAP enhancements. Each individual SAP enhancement may be used only once in a single customer enhancement program (this guarantees the uniqueness of a customer project).
SAP application programmers preplan function module exits, menu exits, and screen exits for their applications and combine them to create useful enhancements for the R/3 System.
Customers create their own enhancement projects for their systems using SAP enhancements. You can customize the individual components of an enhancement project by creating your own include programs (for function module exits), texts (for menu exits), and subscreens (for screen exits).

Where we can find the detail infomation about the Value String of automatic

Where we can find the detail infomation about the Value String of automatic?
such as WE06,WE01 and so on.

Hai,
           Value string keys are for SAP internal usage. It is just a pointer to the transaction event key which is necessary for automatic account determination.
           Movement types are linked to transaction keys via valuation string in OMWN T-code.
           The R/3 System automatically determines the value string assigned to a specific transaction. It depends partly on entered parameters manually and partly on parameters derived internally by the system. The value string contains all posting transactions that are possible for a certain transaction. The program decides which of these posting transactions lead to G/L account postings in individual cases. You cannot define this in Customizing.
Value string WE01, for the goods receipt for a purchase order into stock, contains transactions BSX and WRX.
WE01: BSX, WRX, PRD, KDM, EIN, EKG, BSV, FRL, FRN, BSX, UMB.
WA14: BSX ,PRD, BSX, UMB
WA01: BSX, GBB, PRD, BSX, UMB
Value string RE05 contains transactions BSX and UMB.
In the standard system, value string WE01 is assigned to goods receipts (and also cancellations and return deliveries) for Standard and Subcontracting purchase order items without account assignment concerning valuated material into stock. In the case of (valuated) goods receipts for purchase order items not subject to account assignment,
post the items to a stock account using the transaction key BSX and make an offsetting entry to a GR/IR clearing account. A price difference posting (transaction key PRD) is only used if the valuated material is subject to standard price control and if the order price (or invoice price) is different from the standard price. Transaction key KDM is required in Inventory Management for purchase orders in foreign currencies because of differences in exchange rates between goods receipts and invoice receipts, unless the material can not be debited or credited because it is subject to standard price control.
The transaction keys EIN and EKG (and possibly FRE see account determination for delivery costs) are only used in company codes where purchase account management is active (as required in France and Belgium for example).
The transaction keys BSV, FRL, and FRN are only used for the Subcontracting item category.
Value string WA14 is defined for deliveries without charge (movement type 511).
The following scenarios are possible:
Delivery without charge for material subject to moving average price control → No accounting document
Delivery without charge for material subject to standard price control (and if the posting date is in the previous period standard price in the posting period = standard price in the current period) → Inventory posting (receipt at standard price) and offsetting entry to price differences account
Delivery without charge for material subject to standard price control, with posting date in the previous period and the standard price in the posting period is different to the standard price in the current period → Inventory posting (receipt at standard price) and offsetting entry to price differences account (posting in the previous period) → Stock correction posting and Revenue/expense from revaluation (posting in the current period)
In the standard system, value string WA01 is assigned to goods issues and other goods receipts. The R/3 System uses an additional influencing factor, account grouping, to differentiate further between the various movements during account determination.
Hope it will be Helpful 4 u.
Reward Point if Useful.

ISA Customer Details Search

Hi Forum,
The problem scenario as follows:
While creating the order in ISA in BOB scenario, customer number is required to be entered. During order simulate, it shows the customer details.
I want to know how this customer details are fetched from R/3 and the Function Module called to get the customer details.
Thanks and Regards,
Prashil

Surya,
You need Customer search in BOB scenario.
Try to alter value in "helpvalues-config.xml" file. Find below code of line and change value there.
<helpValuesSearch name = "Customer"
                   type = "extended"
                   description="gs.result.msg.cust.n"
                   maxRow = "20" >
or you can change "maxhits.search.action.businesspartner" parameter value in UI Component in XCM.
I hope you are able to resolve your issue.
Regards.
Ecommerce Developer.

How can I display error log of a standard program in my custom program?

Hello Experts,
I have a requirement where I submit a standard program from my custom module pool program as a background job. I use the TO SAP-SPOOL and thus the log is available when I go to SM37 and check the spool list. I have a requirement that I display this log in a tab within my module pool after the completion of the program. I am unable to fins a proper solution to this. I have both the spool number & the log number but I am unable to find function modules which will help me print them within my program. I found many ways to display it but as full screen and not with in my program.
Could someone please help me with this.
Thank You

Hi,
FM to read a spool request is "RSPO_RETURN_ABAP_SPOOLJOB".
If the error log is displayed as a list output in the standard program, you can also use the syntax SUBMIT Program... and RETURN with export to memory addition.
Then you will be able to read the list output from memory.
Regards,
Munesh.

Zreport for vendor customer details.

Hi ,
I have to create a report tto display a vendor and customer details. on screen i have customer code and vendor code with company code and fiscal year. when i select the cust. code plant and year it will show the doc.no ,post. and doc. date,doc type ,qty and amount as per customer details.
after that as per billing doc. of specific customer ,select excise invoice number and match it with reference number (xblnr) of vendor code. and once it is matched select tht vendor doc.no. post. and doc. date amount and qty and display it in report.so how to right a coding for thesame
let me know as its urgent.
Rgrs
Suchita

please find below coding for your reference.
*& Report ZFI_VEND_CUST_DETAILS
REPORT ZFI_VEND_CUST_DETAILS
NO STANDARD PAGE HEADING
          LINE-COUNT 65
          MESSAGE-ID 00.
TABLES: BSID,BSIK.
DATA: IT_BSID LIKE BSID OCCURS 0 WITH HEADER LINE.
DATA: IT_BSIK LIKE BSIK OCCURS 0 WITH HEADER LINE.
DATA: IT_J_1IEXCHDR LIKE J_1IEXCHDR OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF IT_OUT OCCURS 0,
        BELNR LIKE BSID-BELNR,        " added On 17.04.2007
        BLDAT LIKE BSID-BLDAT,
        BUDAT LIKE BSID-BUDAT,
        BLART LIKE BSID-BLART,
        NAME LIKE KNA1-NAME1,                           "Name 1
        MATNR LIKE VBRP-MATNR,    "Material Number
        ARKTX LIKE VBRP-ARKTX,          "Material description
        FKIMG LIKE VBRP-FKIMG,          "Quantity mentioned in the excise invoice
        VBELN LIKE BSID-VBELN,          "Billing Document
        BUKRS LIKE BSID-BUKRS,
       NAME1 LIKE LFA1-NAME1,
        KUNNR LIKE BSID-KUNNR,
        WRBTR LIKE BSID-WRBTR,
        DMBTR LIKE BSID-DMBTR,
        ZUONR LIKE BSID-ZUONR,
       XBLNR LIKE BSID-XBLNR,
       MENGE LIKE VBRP-MENGE,
       LIFNR LIKE BSIK-LIFNR,        "VENDOR CODE
        EXNUM LIKE J_1IEXCHDR-EXNUM,
        BELNR1 LIKE BSIK-BELNR,        " added On 17.04.2007
        BLDAT1 LIKE BSIK-BLDAT,
        BUDAT1 LIKE BSIK-BUDAT,
       BLART LIKE BSID-BLART,
       NAME LIKE KNA1-NAME1,                           "Name 1
       MATNR LIKE VBRP-MATNR,    "Material Number
       ARKTX LIKE VBRP-ARKTX,          "Material description
       FKIMG1 LIKE VBRP-FKIMG,          "Quantity mentioned in the excise invoice
       VBELN LIKE BSID-VBELN,          "Billing Document
       BUKRS LIKE BSID-BUKRS,
        NAME1 LIKE LFA1-NAME1,
       KUNNR LIKE BSID-KUNNR,
       WRBTR LIKE BSID-WRBTR,
        DMBTR1 LIKE BSIK-DMBTR,
       ZUONR LIKE BSID-ZUONR,
        XBLNR LIKE BSIK-XBLNR,
       MENGE LIKE VBRP-MENGE,
        LIFNR LIKE BSIK-LIFNR,
        END OF IT_OUT.
*DATA: IT_OUT1 LIKE IT_OUT OCCURS 0 WITH HEADER LINE.
*ALV VARIABLES AND INTERNAL TABLES
TYPE-POOLS: SLIS.
DATA: IS_LAYOUT     TYPE SLIS_LAYOUT_ALV,
      IT_FIELDCAT   TYPE SLIS_T_FIELDCAT_ALV,
      IT_LISTHEADER TYPE SLIS_T_LISTHEADER,
      IT_EVENTS     TYPE SLIS_T_EVENT,
      IT_PRINT      TYPE SLIS_PRINT_ALV OCCURS 1 WITH HEADER LINE.
*SELECTION SCREEN DEFINITIONS
SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : SO_KUNNR FOR   BSID-KUNNR,
                 SO_LIFNR FOR   BSIK-LIFNR,
                 SO_BLART FOR   BSID-BLART.
PARAMETER      : P_BUKRS LIKE   BSID-BUKRS OBLIGATORY,
                 P_GJAHR LIKE   BSID-GJAHR OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B.
*START-OF-SELECTION
START-OF-SELECTION.
PERFORM GET_DATA.
PERFORM DISPLAY_DATA.
*&      Form GET_DATA
      text
--> p1        text
<-- p2        text
form GET_DATA .
SELECT * FROM BSID
INTO TABLE IT_BSID
WHERE KUNNR IN SO_KUNNR AND
BUKRS = P_BUKRS AND
GJAHR = P_GJAHR.
LOOP AT IT_BSID.
IT_OUT-BELNR = IT_BSID-BELNR.
IT_OUT-BUKRS = IT_BSID-BUKRS.
IT_OUT-KUNNR = IT_BSID-KUNNR.
IT_OUT-ZUONR = IT_BSID-ZUONR.
IT_OUT-DMBTR = IT_BSID-DMBTR.
IT_OUT-VBELN = IT_BSID-VBELN.
IT_OUT-XBLNR = IT_BSID-XBLNR.
IT_OUT-BLART = IT_BSID-BLART.
IT_OUT-BUDAT = IT_BSID-BUDAT.
IT_OUT-BLDAT = IT_BSID-BLDAT.
APPEND IT_OUT.
ENDLOOP.
*SELECT * FROM J_1IEXCHDR
*INTO IT_J_1IEXCHDR
*WHERE RDOC = IT_OUT-VBELN.
*LOOP AT IT_J_1IEXCHDR.
IT_OUT-EXNUM = IT_J_1IEXCHDR-EXNUM.
**ENDLOOP.
*SELECT * FROM BSIK
*INTO TABLE IT_BSIK
*WHERE XBLNR = IT_OUT-EXNUM AND
*LIFNR IN SO_LIFNR AND
*BUKRS = P_BUKRS AND
*GJAHR = P_GJAHR.
*LOOP AT IT_BSIK.
*IT_OUT-BELNR1 = IT_BSIK-BELNR.
**IT_OUT-BUKRS = IT_BSIK-BUKRS.
*IT_OUT-LIFNR = IT_BSIK-LIFNR.
**IT_OUT-ZUONR = IT_BSIK-ZUONR.
*IT_OUT-DMBTR1 = IT_BSIK-DMBTR.
*IT_OUT-XBLNR = IT_BSIK-XBLNR.
**IT_OUT-BLART = IT_BSIK-BLART.
*IT_OUT-BUDAT1 = IT_BSIK-BUDAT.
*IT_OUT-BLDAT1 = IT_BSIK-BLDAT.
*APPEND IT_OUT.
*ENDLOOP.
*ENDLOOP.
*ENDSELECT.
*SORT IT_OUT BY KUNNR.
LOOP AT IT_OUT.
SELECT SINGLE EXNUM FROM J_1IEXCHDR
INTO IT_OUT-EXNUM
WHERE RDOC = IT_OUT-VBELN.
SELECT BELNR LIFNR DMBTR XBLNR BUDAT BLDAT
FROM BSIK INTO (IT_OUT-BELNR1,IT_OUT-LIFNR,IT_OUT-DMBTR1,IT_OUT-XBLNR,IT_OUT-BUDAT1,IT_OUT-BLDAT1)
WHERE XBLNR = IT_OUT-EXNUM.
ENDSELECT.
SELECT SINGLE NAME1            "NAME OF CUSTOMER
           FROM KNA1
           INTO IT_OUT-NAME
           WHERE KUNNR = IT_OUT-KUNNR.
SELECT SINGLE NAME1            "NAME OF VENDOR
               FROM LFA1
               INTO IT_OUT-NAME1
               WHERE LIFNR = IT_OUT-LIFNR.
SELECT MATNR ARKTX FKIMG
           FROM VBRP
           INTO (IT_OUT-MATNR,IT_OUT-ARKTX,IT_OUT-FKIMG)
           WHERE VBELN = IT_OUT-VBELN AND
                 WERKS = P_BUKRS.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
EXPORTING
    input         = IT_OUT-MATNR
IMPORTING
   OUTPUT        = IT_OUT-MATNR.
MODIFY IT_OUT.
CLEAR IT_OUT.
ENDSELECT.
ENDLOOP.
endform.                    " GET_DATA
*&      Form DISPLAY_DATA
      text
--> p1        text
<-- p2        text
form DISPLAY_DATA .
PERFORM FILL_LAYOUT_STRUCTURE.
PERFORM ALV_HEADER USING IT_LISTHEADER.
PERFORM FILL_FIELDCAT USING :
      'BLDAT'    'DOC Date'             10 'IT_OUT' SPACE SPACE,
      'BUDAT'    'Post.Date'            10 'IT_OUT' SPACE SPACE,
      'KUNNR'    'Customer Code'        10 'IT_OUT' SPACE SPACE,
      'NAME'     'Customer Name'        35 'IT_OUT' SPACE SPACE,
      'LIFNR'    'VENDOR CODE'          10 'IT_OUT' SPACE SPACE,
      'NAME1'    'VENDOR DESC'          35 'IT_OUT' SPACE SPACE,
      'BLART'    'Doc. Type'             2 'IT_OUT' SPACE SPACE,
      'VBELN'    'BILLING DOC NO.'      10 'IT_OUT' SPACE SPACE,
      'BELNR'    'Account Doc. No.'     10 'IT_OUT' SPACE SPACE,
      'DMBTR'    'AMOUNT IN LOCAL'      13 'IT_OUT' SPACE SPACE,
      'MATNR'    'Material Code'        10 'IT_OUT' SPACE SPACE,
      'ARKTX'    'Material DESC'        35 'IT_OUT' SPACE SPACE,
      'FKIMG'    'QTY'                  12 'IT_OUT' SPACE SPACE,
      'ZUONR'    'ASSIGNNMENT'          18 'IT_OUT' SPACE SPACE,
      'EXNUM'    'Excise inv no.'       13 'IT_OUT' SPACE SPACE,
      'BELNR1'   'Account Doc. No.'     10 'IT_OUT' SPACE SPACE,
      'BLDAT1'   'DOC Date'             10 'IT_OUT' SPACE SPACE,
      'BUDAT1'   'Post.Date'            10 'IT_OUT' SPACE SPACE,
      'DMBTR1'   'AMOUNT IN LOCAL'      13 'IT_OUT' SPACE SPACE,
      'XBLNR'    'REFERENCE DOC'        10 'IT_OUT' SPACE SPACE.
PERFORM ALV_EVENTS USING IT_EVENTS.
PERFORM ALV_PRINT.
PERFORM ALV_DISPLAY.
endform.                    " DISPLAY_DATA
*&      Form FILL_LAYOUT_STRUCTURE
      text
--> p1        text
<-- p2        text
form FILL_LAYOUT_STRUCTURE .
DATA: WA_EVENT       TYPE SLIS_ALV_EVENT,
        WA_LISTHEADER TYPE SLIS_T_LISTHEADER.
CLEAR IS_LAYOUT.
IS_LAYOUT-ZEBRA = 'X'.
     is_layout-F2CODE = '&ETA'.
     is_layout-detail_popup = 'X'.
IS_LAYOUT-INFO_FIELDNAME = 'COL_LINE'.
endform.                    " FILL_LAYOUT_STRUCTURE
*&      Form FILL_FIELDCAT
      text
     -->P_0606   text
     -->P_0607   text
     -->P_10     text
     -->P_0609   text
     -->P_SPACE text
     -->P_SPACE text
form FILL_FIELDCAT using    F D O T TO P.
DATA WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
STATICS POS LIKE SY-INDEX VALUE 1.
POS = POS + 1.
CLEAR WA_FIELDCAT.
MOVE : 1     TO   WA_FIELDCAT-ROW_POS,
         POS   TO   WA_FIELDCAT-COL_POS,
         F     TO   WA_FIELDCAT-FIELDNAME,
         D     TO   WA_FIELDCAT-SELTEXT_L,
         O     TO   WA_FIELDCAT-OUTPUTLEN,
         T     TO   WA_FIELDCAT-TABNAME,
         TO    TO   WA_FIELDCAT-DO_SUM,
         P     TO   WA_FIELDCAT-FIX_COLUMN.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
endform.                    " FILL_FIELDCAT
FORM ALV_EVENTS USING EVENTS TYPE SLIS_T_EVENT.
DATA : WA_EVENTS TYPE SLIS_ALV_EVENT.
CLEAR WA_EVENTS.
WA_EVENTS-NAME = 'TOP_OF_PAGE'(001).
WA_EVENTS-FORM = 'TOP_OF_PAGE'.
APPEND WA_EVENTS TO IT_EVENTS.
ENDFORM.                    "alv_events
*&      Form ALV_DISPLAY
      text
--> p1        text
<-- p2        text
form ALV_DISPLAY .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                = ' '
I_BUFFER_ACTIVE                   = ' '
     I_CALLBACK_PROGRAM                = SY-REPID
I_CALLBACK_PF_STATUS_SET          = ' '
     I_CALLBACK_USER_COMMAND           = 'CALL_TCODE'
     I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
I_GRID_TITLE                      =
I_GRID_SETTINGS                   =
     IS_LAYOUT                         = IS_LAYOUT
     IT_FIELDCAT                       = IT_FIELDCAT
IT_EXCLUDING                      =
IT_SPECIAL_GROUPS                 =
   IT_SORT                           = i_sort[]
IT_FILTER                         =
IS_SEL_HIDE                       =
     I_DEFAULT                         = 'X'
     I_SAVE                            = 'A'
IS_VARIANT                        =
     IT_EVENTS                         = IT_EVENTS
IT_EVENT_EXIT                     =
     IS_PRINT                          = IT_PRINT
IS_REPREP_ID                      =
I_SCREEN_START_COLUMN             = 0
I_SCREEN_START_LINE               = 0
I_SCREEN_END_COLUMN               = 0
I_SCREEN_END_LINE                 = 0
I_HTML_HEIGHT_TOP                 = 0
I_HTML_HEIGHT_END                 = 0
IT_ALV_GRAPHICS                   =
IT_HYPERLINK                      =
IT_ADD_FIELDCAT                   =
IT_EXCEPT_QINFO                   =
IR_SALV_FULLSCREEN_ADAPTER        =
IMPORTING
E_EXIT_CAUSED_BY_CALLER           =
ES_EXIT_CAUSED_BY_USER            =
   TABLES
      T_OUTTAB                          = IT_OUT
   EXCEPTIONS
     PROGRAM_ERROR                     = 1
     OTHERS                            = 2
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " ALV_DISPLAY
*FORM FOR TOP OF PAGE
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY = IT_LISTHEADER.
ENDFORM.                    "top_of_page
*&      Form alv_header
FORM alv_header USING    P_IT_LISTHEADER.
data : wa_listheader type slis_listheader.
data : v_date1(10).
data : v_date2(10).
data : v_kunnr1 LIKE bsid-kunnr.
data : v_kunnr2 LIKE bsid-kunnr.
data : v_name1 like t001w-name1.
clear wa_listheader.
wa_listheader-typ = 'H'.
move 'DETAILED CUSTOMER VENDOR DETAILS'
to wa_listheader-info.
append wa_listheader to it_listheader.
select single name1
     from t001w
     into v_name1
     where werks = p_bukrs.
clear wa_listheader.
wa_listheader-typ = 'S'.
wa_listheader-key = 'Plant'.
move v_name1
to wa_listheader-info.
append wa_listheader to it_listheader.
write so_budat-low to v_date1 dd/mm/yyyy no-gap.
write so_budat-high to v_date2 dd/mm/yyyy no-gap.
if so_budat-low is not initial and so_budat-high is not initial.
   clear wa_listheader.
   wa_listheader-typ = 'S'.
   wa_listheader-key = 'Date '.
   concatenate v_date1 ' To ' v_date2 into
                       wa_listheader-info separated by space.
   wa_listheader-info = wa_listheader-info.
   append wa_listheader to it_listheader.
elseif so_budat-low is initial and so_budat-high is initial.
   clear wa_listheader.
   wa_listheader-typ = 'S'.
   wa_listheader-key = 'Date '.
   wa_listheader-info = '*'.
   append wa_listheader to it_listheader.
elseif so_budat-high is initial.
   clear wa_listheader.
   wa_listheader-typ = 'S'.
   wa_listheader-key = 'Date '.
   wa_listheader-info = v_date1.
   append wa_listheader to it_listheader.
endif.
v_kunnr1 = so_kunnr-low.
v_kunnr2 = so_kunnr-high.
if so_kunnr-low is not initial and so_kunnr-high is not initial.
   clear wa_listheader.
   wa_listheader-typ = 'S'.
   wa_listheader-key = 'Customer '.
   concatenate v_kunnr1 ' To ' v_kunnr2 into
                       wa_listheader-info separated by space.
   wa_listheader-info = wa_listheader-info.
   append wa_listheader to it_listheader.
elseif so_kunnr-low is initial and so_kunnr-high is initial.
   clear wa_listheader.
   wa_listheader-typ = 'S'.
   wa_listheader-key = 'Customer '.
   wa_listheader-info = '*'.
   append wa_listheader to it_listheader.
elseif so_kunnr-high is initial.
   clear wa_listheader.
   wa_listheader-typ = 'S'.
   wa_listheader-key = 'Customer '.
   wa_listheader-info = v_kunnr1.
   append wa_listheader to it_listheader.
endif.
ENDFORM.                    " alv_header.
waiting for ur reply.
Thanx
Suchita

Table name to find customer and which sales area he belongs to?

Table name to find customer and which sales area he belongs to?

Hi suchita,
You can find these information Sales area he belongs and all in the table of KNVV , take the customer number from customer master KNA1-KUNNR put it in KNVV-KUNNR. you can find all the sales details.
if you need more info send breaf requirement.
if helpful award the points
Regards
Ram

Cutom T-Code for seding customer details thru IDoc Debmas

Hi Experts,
I have a requirment where in.. I need to send customer details thru IDoc from a custom screen which has cutomer text box and a submit button. After entering cutomer and clicking on submit debmas06 Idoc has to be triggered.
I am not an ABAP expert... please help me with process on devloping the above reqirment.
This is a critical requirment please help ASAP.
Thanks,
Suma

Hi,
u have to use standalone program..iam giving one sample code..aong with u have define the RFC (SM59,WE21(Create port),WE20(create partner profile,BD64 distribute model view)...u have to do..
when u press on submit button,,,
*& Report ZZ_Program_To_Create_Idoc
report zz_program_to_create_idoc .
tables: ekko,ekpo.
selection-screen skip 3.
selection-screen begin of block b1 with frame title titl.
selection-screen skip.
select-options s_ebeln for ekko-ebeln.
selection-screen skip.
selection-screen end of block b1.
data: header_segment_name like edidd-segnam value 'Z1EKKO',
item_segment_name like edidd-segnam value 'Z1EKPO',
idoc_name like edidc-idoctp value 'Z19838IDOC1'.
data: header_segment_data like z1ekko,
item_segment_data like z1ekpo.
data: control_record like edidc.
data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
data: i_communication like edidc occurs 0 with header line,
i_data like edidd occurs 0 with header line.
data: begin of i_ekko occurs 0,
ebeln like ekko-ebeln,
aedat like ekko-aedat,
bukrs like ekko-bukrs,
bsart like ekko-bsart,
lifnr like ekko-lifnr,
end of i_ekko.
data: begin of i_ekpo occurs 0,
ebelp like ekpo-ebelp,
matnr like ekpo-matnr,
menge like ekpo-menge,
meins like ekpo-meins,
netpr like ekpo-netpr,
end of i_ekpo.
start-of-selection.
select ebeln aedat bukrs bsart lifnr from ekko
into table i_ekko where ebeln in s_ebeln.
select ebelp
matnr
menge
meins
netpr
from ekpo
into table i_ekpo
where ebeln in s_ebeln.
control_record-mestyp = messagetyp.
control_record-rcvprt = 'LS'.
control_record-idoctp = idoc_name.
control_record-rcvprn = '0MART800'.
loop at i_ekko.
header_segment_data-ebeln = i_ekko-ebeln.
header_segment_data-aedat = i_ekko-aedat.
header_segment_data-bukrs = i_ekko-bukrs.
header_segment_data-bsart = i_ekko-bsart.
header_segment_data-lifnr = i_ekko-lifnr.
i_data-segnam = header_segment_name.
i_data-sdata = header_segment_data.
append i_data.
select ebelp
matnr
menge
meins
netpr
from ekpo
into table i_ekpo
where ebeln = i_ekko-ebeln.
loop at i_ekpo.
item_segment_data-ebelp = i_ekpo-ebelp.
item_segment_data-matnr = i_ekpo-matnr.
item_segment_data-menge = i_ekpo-menge.
item_segment_data-meins = i_ekpo-meins.
item_segment_data-netpr = i_ekpo-netpr.
i_data-segnam = item_segment_name.
i_data-sdata = item_segment_data.
append i_data.
endloop.
clear i_ekpo.
refresh i_ekpo.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
master_idoc_control = control_record
OBJ_TYPE = ''
CHNUM = ''
tables
communication_idoc_control = i_communication
master_idoc_data = i_data
exceptions
error_in_idoc_control = 1
error_writing_idoc_status = 2
error_in_idoc_data = 3
sending_logical_system_unknown = 4
others = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
loop at i_communication.
write: 'IDOC GENERATED', i_communication-docnum.
endloop.
commit work.
endif.
initialization.
titl = 'ENTER THE PURCHASE ORDER NUMBER'.
Regards,
Nagaraj

To find Custom Developed Function Module -Belonging to a Development Class

Hi Experts,
How to find custom developed function modules belong to a particular development class.
Or Funtion Group belonging to a particular development class.
Thanks in Advance,
Regards,
IFF

Hi,
Ofcourse you can get function group or function module associated with a Development class from Transaction SE80 or SE84.
Step-by-step.
1. From SAP start call transaction se84.
2. Expand Program Library
3. Select Function Group or Function Module
4. In the standard selections give the 'Package' as the name of your development class.
You will get the list of all function modules associated with your development class. The function modules starts with 'Z' or 'Y' will be the custom developed ones.
Regards,
Renjith Michael.

How can I find Custom Sapscirpts

How can I find custom Sapscripts in my existing system
regards
AJ

AJ,
Z* in SE71 and SMARTFORMS.You can also check the table TNAPR as well as TTXFP to know the print programs of the respective forms.
K.Kiran.

How do I find customer exits quickly using SE80,SE81 or other transactions?

Hello all,
Is there a way of using SE80 or SE81 or any other transaction for that matter, to quickly find customer or user exists being used within a given program rather than doing a global search for CALL CUSTOMER within the program? Example, transaction EG31 (Installation Full) which runs the program SAPLE30D.
In SE80 there seem to be no reference to user or customer exits. As for SE81 I was unable to relate SAPLE30D with an application component, or at least I don't know how to do it.
In the Repository Info System (SE81 also) there is a reference to customer exits, but, you MUST know which project is tied to your program, otherwise you'll be chasing your tail!
I guess you can say the easiest way would be to do a global search in the program using the CALL CUSTOMER key words.
Well, I tried that too. The first set of results pointed to INCLUDES which turned out to be empty exits! That is, no code. So, by pure chance and unknowingly, I stumbled upon a customer exit which was the source of my errors. How I did it, I cannot remember. But the problem is that this exit was hidden in a program which was called by SAPLE30D at a later stage.
So, all this searching took a long time and more importantly, it was a lucky find. Not a methodic approach.
So the question is: How do I find customer exits quickly using SE80, SE81 or any other transaction for that matter?
Your help is greatly appreciated.

edited
Edited by: abhinay chelamcherla on Feb 24, 2008 9:49 AM

How to submit a concurrent program from a custom form.

I'm use Forms [32 Bit] Version 6.0.8.26.0 (Production) and Oracle Applications : 11.5.10.2.
I need execute a concurrent program from a custom form.
In the custom form I have a button and when that button is clicked I want to submit this cocurrent program. I am using the below code.
fnd_profile.get('USER_ID', v_user_id);
fnd_profile.get('RESP_ID', v_resp_id);
fnd_profile.get('RESP_APPL_ID', v_resp_appl_id);
fnd_global.apps_initialize(v_user_id,v_resp_id,v_resp_appl_id);
vn_request_id := apps.fnd_request.submit_request (
'XBOL',
'CSUV_GL_STATEMENT_EXPORT'
,NULL
,NULL
,FALSE
commit;
But the concurrent program finished in error:
"ORACLE error 6550 in FDPSTP
Cause: FDPSTP failed due to ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'MAIN'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
The SQL statement being execute"
The executable of the concurrent program is the next:
PACKAGE CSUV_GL_STATEMENT_EXPORT_PK
IS
PROCEDURE Main (
pouc_errbuf OUT VARCHAR2,
poun_retcode OUT NUMBER,
pinc_OWNER in varchar2,
pinc_VESSEL in varchar2,
pind_GL_DATE in varchar2,
pinc_STATE_NUM in varchar2,
pind_STATE_DATE in varchar2,
pinc_EXCEL_LAYOUT in varchar2
END CSUV_GL_STATEMENT_EXPORT_PK;
And de value set of the all my concurrent program parameters is "240 Characters".
I dont't understand why the concurrent program finished wrong.

Hi,
Cause: FDPSTP failed due to ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'MAIN'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignoredPlease refer to "Oracle Applications Developer's Guide" manual for the correct syntax and the number of arguments you need to pass to this API.
Oracle Applications Developer's Guide
http://download.oracle.com/docs/cd/B25516_18/current/acrobat/115devg.pdf
Thanks,
Hussein

Program to Find Customer Details

Similar Messages

Maybe you are looking for