Salesorder function module

Hi,
can any one help me in developing a function module which generates sales order.
Regards,
chandu.

Hi,
To create the sales order,
If u want to create the sales order then t-code is VA01 and if u want to use the fm then go through the below code.
FORM salesdocu changing P_HEADER like header
                         P_HEADERX like headerx
                         Pt_ITEM   like t_item[]
                         Pt_ITEMX like t_itemx[]
                         P_LT_SCHEDULES_IN like lt_schedules_in[]
                         P_LT_SCHEDULES_INX like lt_schedules_inx[]
                         Pt_PARTNER like t_partner[]
                         P_V_VBELN like v_vbeln.
perform sales_fill_data changing p_header
                                   p_headerx
                                   pt_item
                                   pt_itemx
                                   p_lt_schedules_in
                                   p_lt_schedules_inx
                                   pt_partner.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
      sales_header_in     = p_header
      sales_header_inx    = p_headerx
    IMPORTING
      salesdocument_ex    = p_v_vbeln
    TABLES
      return              = t_return
      sales_items_in      = pt_item
      sales_items_inx     = pt_itemx
      sales_schedules_in = p_lt_schedules_in
      sales_schedules_inx = p_lt_schedules_inx
      sales_partners      = pt_partner.
perform commit_work.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    WRITE / return-message.
    EXIT.
ENDLOOP.
WRITE: / ' Sales Document    :', v_vbeln.
perform delivery_creation.             " DELIVERY ORDER CREATION
ENDFORM.                    " salesdocu
FORM sales_fill_data changing P_HEADER like header
                                P_HEADERX like headerx
                                Pt_ITEM   like t_item[]
                                Pt_ITEMX like t_itemx[]
                                P_LT_SCHEDULES_IN like lt_schedules_in[]
                                P_LT_SCHEDULES_INX like lt_schedules_inx
                                Pt_PARTNER like t_partner[].
p_header-doc_type = w_auart.
p_headerx-doc_type = 'X'.
p_header-sales_org = w_vkorg.
p_headerx-sales_org = 'X'.
p_header-distr_chan = w_vtweg.
p_headerx-distr_chan = 'X'.
p_header-division = w_spart.
p_headerx-division = 'X'.
p_headerx-updateflag = 'I'.
fs_patnr-partn_role = 'AG'.
fs_patnr-partn_numb = w_sold.
APPEND fs_patnr to pt_partner.
fs_patnr-partn_role = 'WE'.
fs_patnr-partn_numb = w_ship.
APPEND fs_patnr to pt_partner.
loop at it_item.
    CLEAR fs_ITEM.
    fs_item-material = it_item-matnr.
    fs_item-plant = it_item-plant.
    fs_item-target_qty = it_item-menge.
    fs_item-target_qu = 'ST'.
    fs_item-item_categ = it_item-itcat.
    APPEND fs_item to pt_item.
    W_COUNTER = W_COUNTER + 1.
endloop.
DO W_COUNTER TIMES.
    fs_itemx-updateflag = 'I'.
    fs_itemx-material = 'X'.
    fs_itemx-plant = 'X'.
    fs_itemx-target_qty = 'X'.
    fs_itemx-target_qu = 'X'.
    fs_itemx-item_categ = 'X'.
    APPEND fs_itemx to pt_itemx.
ENDDO.
    Fill schedule lines
LOOP AT IT_ITEM.
    CLEAR fs_sin.
    fs_sin-itm_number = IT_NUM.
    fs_sin-sched_line = IT_LINE.
    fs_sin-req_qty = IT_ITEM-menge.
    APPEND fs_sin to p_lt_schedules_in.
    IT_NUM = IT_NUM + 10.
    IT_LINE = IT_LINE + 1.
ENDLOOP.
IT_NUM = '000010'.
IT_LINE = '0001'.
    Fill schedule line flags
LOOP AT IT_ITEM.
    CLEAR fs_sinx.
    fs_sinx-itm_number = IT_NUM.
    fs_sinx-sched_line = IT_LINE.
    fs_sinx-updateflag = 'X'.
    fs_sinx-req_qty = 'X'.
    APPEND fs_sinx to p_lt_schedules_inx.
    IT_NUM = IT_NUM + 10.
    IT_LINE = IT_LINE + 1.
ENDLOOP.
ENDFORM.                    " sales_fill_data
Plzz reward points if it helps.

Similar Messages

Function module for document flow

Hi,
I am developing a report on sales.
i need to display the delivery and billing status of the sale order in the report.
Is there any function module to get both the delivery and billing status for the input parameter sale order number.....?
Thanks in advance....
Raghav

hi , check the code
REPORT ZEX2 MESSAGE-ID arc NO STANDARD PAGE HEADING.
Tables :kna1,vbak.
SELECT-OPTIONS : so_vkorg FOR vbak-vkorg OBLIGATORY,
 so_vtweg FOR vbak-vtweg OBLIGATORY,
 so_spart FOR vbak-spart,
 so_kunnr FOR kna1-kunnr.
DATA : BEGIN OF sales_open OCCURS 0 ,
 vbeln LIKE vbak-vbeln,
 auart LIKE vbak-auart,
 kunnr LIKE kna1-kunnr,
 bstnk LIKE vbak-bstnk,
 lfstk LIKE vbuk-lfstk,
 fkstk LIKE vbuk-fkstk,
 gbstk LIKE vbuk-gbstk,
 END OF sales_open.
DATA : BEGIN OF itm_sales OCCURS 0,
 vbeln LIKE vbap-vbeln,
 posnr LIKE vbap-posnr,
 matnr LIKE vbap-matnr,
 lfsta LIKE vbup-lfsta,
 lfgsa LIKE vbup-lfgsa,
 fksta LIKE vbup-fksta,
 fksaa LIKE vbup-fksaa,
 gbsta LIKE vbup-gbsta,
 END OF itm_sales.
DATA : l_kunnr LIKE kna1-kunnr,
 l_vkorg LIKE vbak-vkorg,
 l_vtweg LIKE vbak-vtweg,
 l_spart LIKE vbak-spart.
DATA: v_statusl(20) TYPE c,
 v_statusb(20) TYPE c,
 v_statusf(20) TYPE c,
 v_statusg(20) TYPE c,
 v_status(20) TYPE c,
 v_field(1) TYPE c.
**Selection Screen Validations.
AT SELECTION-SCREEN.
PERFORM validations.
*& Form Validations
 text
--> p1 text
<-- p2 text
FORM validations.
**Customer
IF NOT so_kunnr[] IS INITIAL.
 SELECT SINGLE kunnr INTO l_kunnr
 FROM kna1
 WHERE kunnr IN so_kunnr.
 IF sy-subrc NE 0.
 MESSAGE e002 WITH text-005.
 ENDIF.
ENDIF.
**Sales Organization
IF NOT so_vkorg[] IS INITIAL.
 SELECT SINGLE vkorg INTO l_vkorg
 FROM tvko
 WHERE vkorg IN so_vkorg.
 IF sy-subrc NE 0.
 MESSAGE e003 WITH text-006.
 ENDIF.
ENDIF.
**Distribution Channel
IF NOT so_vtweg[] IS INITIAL.
 SELECT SINGLE vtweg INTO l_vtweg
 FROM tvkov
 WHERE vkorg IN so_vkorg
 AND vtweg IN so_vtweg.
 IF sy-subrc NE 0.
 MESSAGE e004 WITH text-007.
 ENDIF.
ENDIF.
**Division
IF NOT so_spart[] IS INITIAL.
 SELECT SINGLE spart INTO l_spart
 FROM tvta
 WHERE vkorg IN so_vkorg
 AND vtweg IN so_vtweg
 AND spart IN so_spart.
 IF sy-subrc NE 0.
 MESSAGE e005 WITH text-008.
 ENDIF.
ENDIF.
ENDFORM. " Validations
Top-of-page.
PERFORM sales_top_of_page.
Start-of-selection.
PERFORM sales_sel.
*& Form sales_sel
 text
--> p1 text
<-- p2 text
FORM sales_sel.
SELECT vbeln auart kunnr bstnk
 lfstk fkstk gbstk
 INTO TABLE sales_open
 FROM vbakuk
 WHERE vkorg IN so_vkorg
 AND vtweg IN so_vtweg
 AND spart IN so_spart
 AND kunnr IN so_kunnr
 AND gbstk NE 'C'.
LOOP AT sales_open.
 WRITE:/4 sy-vline,
 5 sales_open-vbeln HOTSPOT ON COLOR 2 INTENSIFIED OFF,
 16 sy-vline,
 17 sales_open-auart COLOR 2 INTENSIFIED OFF,
 27 sy-vline,
 28 sales_open-kunnr COLOR 2 INTENSIFIED OFF,
 40 sy-vline,
 41 sales_open-bstnk COLOR 2 INTENSIFIED OFF,
 55 sy-vline,
 56 sales_open-lfstk,
 76 sy-vline,
 77 sales_open-fkstk,
 96 sy-vline,
 97 sales_open-gbstk ,
 117 sy-vline.
 HIDE sales_open-vbeln .
ENDLOOP.
ENDFORM. " sales_sel
*& Form sales_top_of_page
 text
--> p1 text
<-- p2 text
FORM sales_top_of_page.
WRITE:/4 sy-uline(114),
 50 'OPEN SALES ORDERS' COLOR 7 INTENSIFIED ON .
WRITE: /4 sy-vline,
 5 'SalesOrder' COLOR 1 ,
 16 sy-vline,
 17 'OrderType' COLOR 1,
 27 sy-vline,
 28 'Customer' COLOR 1,
 40 sy-vline,
 41 'PoNumber' COLOR 1,
 55 sy-vline,
 56 'Delivery Status' COLOR 1,
 76 sy-vline,
 77 'Billing Status' COLOR 1,
 96 sy-vline,
 97 'Processing Status' COLOR 1,
 117 sy-vline .
WRITE:/4 sy-uline(114).
ENDFORM. " sales_top_of_page
AT LINE-SELECTION.
SELECT a~vbeln
 a~posnr
 a~matnr
 a~kwmeng
 b~lfsta
 b~lfgsa
 b~fksta
 b~fksaa
 b~gbsta
 INTO TABLE itm_sales
 FROM vbap AS a JOIN vbup AS b
 ON avbeln EQ bvbeln
 AND aposnr EQ bposnr
 AND b~gbsta NE 'C'
 WHERE a~vbeln EQ sales_open-vbeln.
IF NOT sales_open IS INITIAL.
 LOOP AT itm_sales.
 WRITE:/5 itm_sales-vbeln,
 itm_sales-posnr,
 itm_sales-matnr,
 itm_sales-lfsta,
 itm_sales-lfgsa,
 itm_sales-fksta,
 itm_sales-fksaa,
 itm_sales-gbsta.
 ENDLOOP.
ENDIF.

Function Module for open Purchase Order & Sales Order?

Hi, commonly I read the data from tables and calculate the open quantity for sales order and purchase order, but I want to know, are there any standard function modules for getting the list of open "purchase order" and "sales order" respectively?
Thanks and Regards.

hi Ren,
u can check all these bapi's related to salesorder
BAPI_SALESORDER_CHANGE Sales order: Change Sales Order
BAPI_SALESORDER_CONFIRMDELVRY Sales Order: Confirmation of Delivery; Document Flow Update
BAPI_SALESORDER_CREATEFROMDAT1 Sales order: Create Sales Order
BAPI_SALESORDER_CREATEFROMDAT2 Sales order: Create Sales Order
BAPI_SALESORDER_CREATEFROMDATA Create Sales Order, No More Maintenance
BAPI_SALESORDER_GETLIST Sales order: List of all Orders for Customer
BAPI_SALESORDER_GETSTATUS Sales Order: Display Status
BAPI_SALESORDER_SIMULATE Sales Order: Simulate Sales Order
May be this FM can help you
MB_ADD_PURCHASE_ORDER_QUANTITY (Reading and adding open purchase order quantities)
Regards,
Naveen

Function module to retrieve the account number linked to an SD invoice item

Hi all,
I should retrieve the gl account number linked to a certain SD invoice item. The
program starts from VBRK and VBRP data. Is there a function module which
enables to get it starting from these header lines? I already used the function
module: RV_INVOICE_ACCOUNT_DETERM ( release: 4.0 ), but in some cases it
doesn't seem to function properly ( the export table TKOMV doesn't contain a
value for the SAKN1 field ). For the invoices for which the function isn't able to
retrieve the account number, the standard accounting analysis functionality returns
the following message: account determination carried out via KOFI type. So I'm
searching for a function module that's able to retrieve the account number in these
cases also.
Thanks in advance.
Adriano.

Dear Adriano,
Try with Function Module 'SD_DETERMINE_ACCOUNT_INVOICE '.
Additional Info:
BAPIs related salesorder:
BAPI_SALESORDER_CHANGE Sales order: Change Sales Order
BAPI_SALESORDER_CONFIRMDELVRY Sales Order: Confirmation of Delivery; Document Flow Update
BAPI_SALESORDER_CREATEFROMDAT1 Sales order: Create Sales Order
BAPI_SALESORDER_CREATEFROMDAT2 Sales order: Create Sales Order
BAPI_SALESORDER_CREATEFROMDATA Create Sales Order, No More Maintenance
BAPI_SALESORDER_GETLIST Sales order: List of all Orders for Customer
BAPI_SALESORDER_GETSTATUS Sales Order: Display Status
BAPI_SALESORDER_SIMULATE Sales Order: Simulate Sales Order
FM:
MB_ADD_PURCHASE_ORDER_QUANTITY (Reading and adding open purchase order quantities)
SD_SALES_ORDER_STATUS_WWW for complete details including the delivery information.
Hope this will help.
Regards,
Naveen.

Different types of function module

hi,
When we create a function module : in one of the tabs we can find
1 general function module
2. remote function module
3. update function module.
What is meant by update function module and remote function module. can anyone explain me with an example and when shd we opt for 2 and 3.
thanxs
hari

Function Modules:
Function modules allow you to encapsulate and reuse global functions in the R/3 System.
They are stored in a central library. The R/3 System contains a wide range of predefined
function modules that you can call from any ABAP program.
Unlike subroutines, you do not define function modules in the source code of your program.
Instead, you use the Function Builder. The actual ABAP interface definition remains hidden
from the programmer. You can define the input parameters of a function module as optional.
You can also assign default values to them. Function modules also support exception handling.
This allows you to catch certain errors while the function module is running. You can test
function modules without having to include them in a program using the Function Builder.
Function Groups:
Function groups are containers for function modules. You cannot execute a function group.
When you call a function module, the system loads the whole of its function group into the
internal session of the calling program.
Calling Function Modules in ABAP:
To call a function module, use the CALL FUNCTION statement:
CALL FUNCTION <module>
[EXPORTING f1 = a 1.... f n = a n]
[IMPORTING f1 = a 1.... f n = a n]
[CHANGING f1 = a 1.... f n = a n]
[TABLES f1 = a 1.... f n = a n]
[EXCEPTIONS e1 = r 1.... e n = r n [ERROR_MESSAGE = r E]
[OTHERS = ro]].
You can specify the name of the function module <module> either as a literal or a variable.
Each interface parameter <fi> is explicitly assigned to an actual parameter <a i>. You can
assign a return value <r i> to each exception <e i>. The assignment always takes the form
<interface parameter> = <actual parameter>. The equals sign is not an assignment operator
in this context.
After EXPORTING, you must supply all non-optional import parameters with values
appropriate to their type. You can supply values to optional import parameters if you
wish.
[email protected]
34
After IMPORTING, you can receive the export parameters from the function module by
assigning them to variables of the appropriate type.
After CHANGING or TABLES, you must supply values to all of the non-optional
changing or tables parameters. When the function module has finished running, the
changed values are passed back to the actual parameters. You can supply values to
optional changing or tables parameters if you wish.
You can use the EXCEPTIONS option to handle the exceptions of the function module. If an
exception <e i > is raised while the function module is running, the system terminates the
function module and does not pass any values from the function module to the program,
except those that were passed by reference. If <e i > is specified in the EXCEPTION option,
the calling program handles the exception by assigning <r i > to SY-SUBRC. <r i > must be a
numeric literal.
If you specify of ERROR_MESSAGE in the exception list you can influence the message
handling of function modules. Normally, you should only call messages in function modules
using the MESSAGE ... RAISING statement. With ERROR_MESSAGE you can force the system
to treat messages that are called without the RAISING option in a function module as follows
for various FM's
http://www.erpgenie.com/abap/functions.htm
Calling Function Modules
http://help.sap.com/saphelp_46c/helpdata/en/9f/db98ef35c111d1829f0000e829fbfe/content.htm
remote enabled fm's are BAPI's
refer
Introduction to BAPIs:
Definition
The SAP Business Objects held in the Business Object Repository (BOR) encapsulate their data
and processes. External access to the data and processes is only possible by means of specific
methods - BAPIs (Business Application Program Interfaces).
A BAPI is defined as a method of a SAP Business Object.
For example, the functionality that is implemented with the SAP Business Object type
"Material" includes a check for the materials availability. Thus, the Business Object type
"Material" offers a BAPI called "Material.CheckAvailability".
Use
To use a BAPI method, an application program only needs to know how to call the method;
that is, it needs to know the methods interface definition. Therefore, when including a BAPI
invocation in your application program, you only need to supply the appropriate interface
information.
A BAPI interface is defined by:
Import parameters, which contain data to be transferred from the calling program to
the BAPI
Export parameters, which contain data to be transferred from the BAPI back to the
calling program
Import/export (table) parameters for both importing and exporting data
Structure
The BAPIs in the R/3 System are currently implemented as function modules, all of which are
held in the Function Builder. Each function module underlying a BAPI:
Supports the Remote Function Call (RFC) protocol
Has been assigned as a method to an SAP Business Object in the BOR
Is processed without returning any screen dialogs to the calling application
Integration
The architecture enables SAP to change the details of a BAPIs implementation without
affecting external applications, which are using the BAPI.
Advantages of Using BAPIs
BAPIs are standardized methods of SAP Business Objects that enable customers and third
parties to integrate their software components with the R/3 System and the Business
Framework.
Business Standard
SAP Business Objects and their BAPIs provide a business content standard, rather than a
technical interoperability standard; that is, they enable the integration of R/3 and other
software components on a business level, not on a technical level.
[email protected]
97
Standards Conformance
BAPIs are being developed as part of the SAP joint initiative with customers, partners, and
leading standards organizations. BAPIs are becoming a communication standard between
business systems.
You can access SAP Business Objects and their BAPIs by using object-oriented interfacing
technologies such as Microsofts COM/DCOM (Component Object Model/Distributed Component
Object Model).
The SAP Business Objects already comply with the Open Applications Group (OAG)
specifications, and, in conjunction with ObjectBridge from VisualEdge, conform to the Object
Management Groups CORBA (Common Object Request Broker Architecture) guidelines.
Stability and Downward Compatibility
Once a BAPI is implemented and released by SAP, its interface definition and parameters
remain stable in the long term, thus ensuring that your application program remains
unaffected by any changes to the underlying R/3 software and data.
SAP can make any necessary extensions to the BAPIs, for example, additional optional
parameters, without destabilizing the operation of existing applications and, at the same time,
can offer the enhanced functionality to new applications.
Object Orientation
As methods of the SAP Business Objects, BAPIs provide access to R/3 data and processes
following an object-oriented programming model. BAPIs can be called using object-oriented
interfacing technologies, such as COM/DCOM, thus enabling software components from SAP
and third parties to interact freely.
Openness
You can access BAPIs from all development platforms that support the SAP Remote Function
Call (RFC) protocol.
BAPI Definition
A Business Application Programming Interface (BAPI) is a precisely defined interface providing
access to processes and data in business application systems such as R/3. BAPIs are defined
as API methods of SAP Business Objects. These business objects and their BAPIs are described
and stored in the Business Object Repository (BOR).
A BAPI is implemented, however, as a function module, that is stored and described in the
Function Builder.
BAPIs can be called within the R/3 System from external application systems and other
programs. BAPIs are the communication standard for business applications. BAPI interface
technology forms the basis for the following developments:
R/3 satellite systems
Isolating components within the R/3 System in the context of Business Framework
Distributed R/3 scenarios using Application Link Enabling (ALE)
Connecting R/3 Systems to the Internet using Internet Application Components (IACs)
Visual Basic programs as front-end to R/3 Systems
Workflow applications that extend beyond system boundaries
Customers and partners own developments
Connections to non-SAP software
Connections to legacy systems
[email protected]
98
Standardized BAPIs
Some BAPIs and methods provide basic functions and can be used for most SAP Business
Objects. Such BAPIs are known as "standardized" BAPIs.
Using the descriptions below as a guide, verify whether you can implement the BAPI as a
standardized BAPI.
Features
BAPIs for Reading Data
The following BAPIs provide you with read-only access to data in the associated business
object:
GetList
With this BAPI you can select a range of object key values, for example, company
codes and material numbers. To specify appropriate selection requirements the calling
program must pass the relevant parameters to the interface. The key values selected
by the BAPI GetList are returned to the calling program in a table, together with other
useful information, for example, short texts. The key values can then be passed on to
another BAPI for further processing, for example, the BAPI GetDetail, as listed below.
GetDetail
The BAPI GetDetail uses a key to retrieve details about an instance(s specific
occurrence) of a business object and returns this data to the calling program.
GetStatus
The BAPI GetStatus is used to query the status of an SAP Business Object, for
example, to display the processing status of a sales order. This BAPI is used only for
displaying the status of an object and does not retrieve full details like the BAPI
GetDetail.
ExistenceCheck
The BAPI ExistenceCheck checks, whether an entry exists for an SAP Business Object,
for example, whether the customer master has been created. You should implement
this method as a workflow method and not as a BAPI (RFC capable function module).
The method CompanyCode.ExistenceCheck of the business object CompanyCode
(BUS0002) is an example of this. This workflow method is indirectly invoked when the
calling program instantiates an object, for example, by using
GetSAPObject("CompanyCode") from within Visual Basic.
BAPIs for Creating or Changing Data
The following BAPIs can create, change or delete instances of a business object: If required,
you can implement these BAPIs so that, several instances of a business object can be created,
deleted or modified simultaneously in the same call. In such cases "multiple" is added to the
method name, for example ChangeMultiple.
BAPIs that can create, change or delete instances are:
Create or CreateFromData
The BAPI Create or CreateFromData creates an instance of an SAP Business Object,
for example, a sales order. Create is the preferred name for this BAPI. Use the name
CreateFromData only when a workflow method called Create already exists for the
business object in question.
[email protected]
99
Change
The BAPI Change changes an existing instance of a SAP Business Object, for example,
a sales order.
Delete
The BAPI Delete deletes an instance of a SAP Business Object, for example, sales
order.
BAPIs for Replicating Business Object Instances
The BAPIs below can be implemented as methods of business objects that can be replicated.
They enable specific instances of an object type to be copied to one or more different systems.
These BAPIs are used mainly to transfer data between distributed systems within the context
of Application Link Enabling (ALE).
The method below must be implemented for each business object to be replicated.
Replicate
The BAPI Replicate is called in the system, which contains the originals of the business
object instances to be replicated. It is used to:
Identify the business objects to be replicated and to organize the required data.
Call the clone methods described below in the receiving system
Moreover, at least one of the clone methods below must be implemented for each business
object to be replicated.
Clone
The BAPI Clone is used by a system to replicate one business object on another
system or to modify one business object that has already been cloned.
CloneMultiple
The BAPI CloneMultiple is used by a system to replicate several business objects on
another system or to modify several business objects that have already been cloned.
Defining and Implementing the BAPI
Purpose
Various components of the ABAP Workbench are used when you define and implement a BAPI.
A BAPI is an API method of a business object and is defined as such in the Business Object
Repository (BOR). However, a BAPI is implemented as an RFC capable function module, which
is maintained in the Function Builder. The definitions and descriptions of the data structures
used by the BAPI are stored in the ABAP Dictionary.
For function modules that implement BAPIs, certain standards and rules must be adhered to
over and above the standard programming rules for function modules. For example, COMMIT
WORK commands must not be used in the function modules that a BAPI is based on.
The following sections guide you through the steps involved in developing a BAPI. The sections
contain information about the guidelines and conventions that you should adhere to when
defining and implementing a BAPI. When implementing BAPIs follow the requirements below
to ensure you achieve consistent behavior and representation of BAPIs as object oriented
methods of SAP Business Objects.
[email protected]
100
BAPI Programming
BAPI Definition
A Business Application Programming Interface (BAPI) is a precisely defined interface providing
access to processes and data in business application systems such as R/3.
BAPIs are defined as API methods of SAP Objects. These objects and their BAPIs are described
and stored in the BOR (BOR).
Use
BAPIs can be called within the R/3 System from external application systems and other
programs. A BAPI call can either be made as an object oriented method call or as a remote
function call (RFC).
BAPIs are a global communication standard for business applications.
Examples of what BAPIs can be used for include:
R/3 satellite systems
Distributed R/3 scenarios using Application Link Enabling (ALE)
Connecting R/3 Systems to the Internet using Internet application components (IACs)
Visual Basic programs as front-end to R/3 Systems
Workflow applications that extend beyond system boundaries
Customers and partners own developments
Connections to non-SAP software
Connections to legacy systems
BOR Definition
The Business Object Repository (BOR) is the object-oriented repository in the R/3 System. It
contains, among other objects, SAP Business Objects and their methods. In the BOR a
Business Application Programming Interface (BAPI) is defined as an API method of an SAP
Business Object. Thus defined, the BAPIs become standard with full stability guarantees as
regards their content and interface.
Use
With regard to SAP Business Objects and their BAPIs, the BOR has the following functions:
Provides an object-oriented view of R/3 System data and processes.
R/3 application functions are accessed using methods (BAPIs) of SAP Business
Objects. Implementation information is encapsulated; only the interface functionality
of the method is visible to the user.
Arranges the various interfaces in accordance with the component hierarchy, enabling
functions to be searched and retrieved quickly and simply.
Manages BAPIs in release updates.
BAPI interface enhancements made by adding parameters are recorded in the BOR.
Previous interface versions can thus be reconstructed at any time. When a BAPI is
created the release version of the new BAPI is recorded in the BOR. The same applies
when any interface parameter is created.
The version control of the function module that a BAPI is based on is managed in the
Function Builder.
Ensures interface stability.
Any interface changes that are carried out in the BOR, are automatically checked for
syntax compatibility against the associated development objects in the ABAP
Dictionary.
[email protected]
101
Integration
You should only define a BAPI as a SAP Business Object method in the BOR if the function
module that the BAPI is based on has been fully implemented. Full access to the BOR is
restricted to the persons responsible for the objects involved and for quality control.
BOR-BAPI Wizard
The BOR-BAPI Wizard assists with creating new BAPI methods in the BOR. It takes you
through the creation process step by step.
Transaction Model for Developing BAPIs Purpose
The transaction model in which BAPIs are used determines how you have to program BAPIs.
The transaction model described here has been used to develop BAPIs for R/3 Releases 3.1
and 4.0A.
Logical Unit of Work (LUW) and Statelessness
Within the context of this transaction model a transaction represents one processing step or
one logical unit of work (LUW). When a transaction is called, database operations are either
fully executed or not at all. The whole transaction must be programmed to be stateless.
This transaction model requires that:
No data is imported that may indirectly affect the result. If a transaction is called more
than once, each call must have the same result. For BAPIs this means, for example,
that Set or Get parameters cannot be used. However, you can keep Customizing data
in a global memory, as this data remains unchanged even if transaction calls are
repeated.
There must be no functional dependencies between two transactions.
Either all relevant data has to be changed in the database or none at all.
Determining the SAP Business Object and Its Key Fields
You have to identify the relevant SAP Business Object in the Business Object Repository (BOR)
and determine whether the key fields of the Business Object are relevant for your BAPI.
A key is defined in the BOR for most SAP Business Objects. This key can consist of several key
fields. The content of these key fields uniquely identifies one individual instance of an SAP
Business Object.
You can differentiate between instance-dependent and instance-independent BAPI methods.
Unlike instance-independent methods, instance-dependent methods relate to one instance
(one specific occurrence) of an SAP Business Object type, for example to one specific sales
order.
In the case of instance-dependent BAPIs, the key fields of the corresponding SAP Business
Object must be used as parameters in the function module the BAPI is based on so that the
associated object instance can be identified. The names of the key fields in the SAP Business
Object and the corresponding parameters in the BAPI function module must be the same,
because the name links the key fields to the parameters.
All the key fields defined in the BOR for the SAP Business Object in question must be used as
the parameters in the function module.
Example
SAP Business Object Creditor has a key field named CreditorId.
This key field must be defined as a parameter with the name CREDITORID in the function
modules of the instant-dependent BAPIs for this Business Object.
[email protected]
102
To display the Business Object and its key fields follow the steps below:
1. Select Tools -> ABAP Workbench -> Overview -> Business Object Browser . The
business objects are displayed in the order of the R/3 application hierarchy.
2. Select the required SAP Business Object in the application hierarchy and double click it
to open it.
3. To display the Business Objects key fields, expand the node Key fields.
Defining the Interface Structure of the BAPI
In this step you are going to define the BAPI interface, that is, the individual import, export
and table parameters required for calling the BAPI.
Caution
You cannot use Changing and Exception parameters in a function module which implements a
BAPI.
Process Flow
To define the interface parameters, proceed as follows:
1. Check whether the key fields of the SAP Business Object are required in the interface. The
key fields of the SAP Business Object are some of the most important BAPI parameters.
If a key value is to be passed to the BAPI by the calling program, the key field must be set as
an import parameter in the function module of the BAPI. That way a specific instance of the
Business Object is identified.
For example, this could be a customer number (CustomerNo) in the BAPIs Customer.GetDetail
and Customer.CheckPassword, or the number of a sales document in the BAPI
SalesOrder.GetStatus.
For BAPIs that generate instances, for example, the BAPIs Create or CreateFromData, the key
field of the Business Object should be set as an export parameter in the BAPI function module.
These BAPIs return one key value, for example, an order number in the BAPI
SalesOrder.CreateFromData.
For BAPIs that are class methods a key field is neither set as an import nor as an export
parameter in the BAPI function module. Class methods are instance-independent and are
called without the use of key values. Usually they return a table with a selection of key values.
2. Specify what other data is relevant as import, export or table parameters for the BAPI.
Every BAPI must have an Export parameter return that reports messages back to the calling
program.
Example
The BAPI to be developed is to read data from the SAP Business Object Creditor. To read
creditor details, the calling program has to pass the ID of the creditor and the company code.
The creditor data returned is to include general details, specific details and bank details.
To map these requirements onto the BAPI interface, the following parameters must be set in
the function module which the BAPI is based on:
The key field CreditorID of the SAP Business Object as an import parameter
An import parameter for the company code
A Return parameter that reports messages back to the calling program
A parameter for general details of the creditor
A parameter for specific details of the creditor
A parameter for bank details of the creditor
for BAPI list
refer www.sapbapi.com
for FM's refer www.se37.com
regards
srinivas
*reward for useful answers*

HOW WE EXTRACT SALES FLOW DATA FROM VBFA TABLE TO BI THROUGH FUNCTION MODUL

HI EXPERTS,
i am working on SD. i need how VBFA data extrcted into BI using function module. how to report relationship between SALESORDER- PGI-INVOICE. can anyone help me.
thanks in advance

Hi,
If you are looking for standard extractor then check the metadata repository, and if you want generic extractor then you can take help of RSAX_BIW_GET_DATA_SIMPLE extractor for writing your own extractors.
Regards,
Durgesh.

Trigger point of function module EXIT_SAPMV45A_002

Who can tell me the trigger point of function module EXIT_SAPMV45A_002?
It is the one of user exits of T-CODE VA01.But it didn't be executed all the time during I executed the T-CODE: VA01 as well as finished the sales document.

HI,
Go to transaction CMOD.
Enter project name and select the button Create
we want to create a project to enahance trasnaction VA01 .
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document.
Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed
Press Save Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '1000'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder.
Note that Sold-to-party now automatically is "1000"
Reward points pls.
Regards,
Govind.

URGENT: Function modules or BAPIs

Hi Experts,
I need function modules or BAPI to get the open items and cleared items G/L Account wise.
Useful replies will be surely awarded.

Hi Chakradhar,
Check tcode : BAPI
u will get all bapis there.
Regards,
Hemant

How to attached class or function module in FD03

Hi Guys
I want to attached CL_ATTACHMENT_LIST for retriving attachment list from fd03 please help to attached the function module in my program?
regards
Piroz
report zfir_aged_debtors no standard page heading
 line-size 255.
Type group
type-pools:
slis. " ALV types
Tables
tables:
adrc, " Addresses
bsad, " Accounting: Customer secondary index (Cleared)
bsid, " Accounting: Customer secondary index (Open)
kna1, " Customer master: General data
knkk, " Customer master: Credit management
knvk. " Customer master: Contact persons
Types
types:
begin of ty_bsadbsid,
 bukrs like bsad-bukrs, " Company code
 kunnr like bsad-kunnr, " Customer
 gjahr like bsad-gjahr, " Fiscal year
 belnr like bsad-belnr, " Accounting document number
 buzei like bsad-buzei, " Line item
 budat like bsad-budat, " Posting date
 bldat like bsad-bldat, " Document date
 waers like bsad-waers, " Currency
 xblnr like bsad-xblnr, " Reference
 shkzg like bsad-shkzg, " Debit/credit indicator
 dmbtr like bsad-dmbtr, " Amount
 zfbdt like bsad-zfbdt, " Baseline date for due date
 " calculation
 zbd1t like bsad-zbd1t, " Cash discount days 1
 zbd2t like bsad-zbd2t, " Cash discount days 2
 zbd3t like bsad-zbd3t, " Net payment terms period
 rebzg like bsad-rebzg, " Number of the invoice
 rebzt like bsad-rebzt, " Follow on document type
end of ty_bsadbsid,
ty_it_bsadbsid type ty_bsadbsid occurs 0,
begin of ty_merged,
 kunnr like kna1-kunnr, " Customer number
 name1 like adrc-name1, " Name
 city1 like adrc-city1, " City
 post_code1 like adrc-post_code1, " Post code
 street like adrc-street, " Street
 house_num1 like adrc-house_num1, " House number
 tel_number like adrc-tel_number, " Telephone number
 fax_number like adrc-fax_number, " Fax number
 namev like knvk-namev, " First name
 namew like knvk-name1, " Last name
 telf1 like knvk-telf1, " Telephone number
 klimk like knkk-klimk, " Credit limit
 skfor like knkk-skfor, " Total receivables
 total like bsad-dmbtr, " Total amount
 rast1 like bsad-dmbtr, " Amount period 1
 rast2 like bsad-dmbtr, " Amount period 2
 rast3 like bsad-dmbtr, " Amount period 3
 rast4 like bsad-dmbtr, " Amount period 4
 rast5 like bsad-dmbtr, " Amount period 5
 rast6 like bsad-dmbtr, " Amount period 6
end of ty_merged,
ty_it_merged type ty_merged occurs 0.
Internal tables
data:
Internal table to store customer line items from BSAD and BSID
it_bsadbsid type ty_it_bsadbsid,
Internal table to store field catalog for ALV function call
it_fieldcat type slis_t_fieldcat_alv,
Internal table to store summarised data for report output
it_merged type ty_it_merged.
Structures
data:
Display variant structures
st_tvariant like disvariant,
st_variant like disvariant.
Constants
constants:
co_delim_dash type c
 value '-',
co_false type c " False
 value space,
co_koart_d like faede-koart " Customer account type
 value 'D',
co_save_u type c " User display variant
 value 'U', " saving allowed.
co_shkzg_h like bsid-shkzg " Debit/Credit indicator
 value 'H', " for credit
co_shkzg_s like bsid-shkzg " Debit/Credit indicator
 value 'S', " for debit
co_selected type c " Value of selected radio
 value 'X', " button or checkbox
co_true type c " True
 value co_selected.
Variables
data:
va_exit type c.
Selection screen definition
selection-screen: begin of block b1 with frame title text-001.
select-options:
s_kunnr for bsad-kunnr. " Customer number
parameters:
p_kkber like knkk-kkber, " Credit control area
p_pafkt like knvk-pafkt, " Contact function
p_datum like sy-datum. " Report date
selection-screen: begin of line,
 comment 01(30) text-006,
 position pos_low.
parameters:
rastbis1 like rfpdo1-allgrogr " Due date sorted 1
 default '000',
rastbis2 like rfpdo1-allgrogr " Due date sorted 2
 default '000',
rastbis3 like rfpdo1-allgrogr " Due date sorted 3
 default '000',
rastbis4 like rfpdo1-allgrogr " Due date sorted 4
 default '000',
rastbis5 like rfpdo1-allgrogr " Due date sorted 5
 default '000'.
selection-screen: end of line.
selection-screen: end of block b1,
 begin of block b2 with frame title text-002.
parameters:
p_varint like disvariant-variant. " Display variant.
selection-screen: end of block b2.
Initialisation
initialization.
Provide default periods for due date sorted list.
rastbis1 = 0.
rastbis2 = 30.
rastbis3 = 60.
rastbis4 = 90.
rastbis5 = 120.
Default report date to current.
p_datum = sy-datlo.
Default credit control area to BP01.
p_kkber = 'BP01'.
At selection screen on value request for
at selection-screen on value-request for p_varint.
Provide display variant list for this program.
call function 'REUSE_ALV_VARIANT_F4'
 exporting
 is_variant = st_variant
 i_save = co_save_u
 importing
 e_exit = va_exit
 es_variant = st_tvariant
 exceptions
 not_found = 2.
if sy-subrc eq 2.
 message id sy-msgid type 'S'
 number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
 if va_exit eq space.
 st_variant = st_tvariant.
 p_varint = st_tvariant-variant.
 endif.
endif.
At selection screen
at selection-screen.
Load display variant.
if not p_varint is initial.
 move st_variant to st_tvariant.
 move p_varint to st_tvariant-variant.
 call function 'REUSE_ALV_VARIANT_EXISTENCE'
 exporting
 i_save = co_save_u
 changing
 cs_variant = st_tvariant.
 st_variant = st_tvariant.
else.
 clear st_variant.
 st_variant-report = sy-repid.
endif.
if p_kkber is initial.
Ensure credit control area is specified.
 message e000(zgen) with 'Credit control area must be specified'.
endif.
if p_pafkt is initial.
Ensure contact person function is specified.
 message e000(zgen) with 'Contact person function must be specified'.
endif.
Start of selection
start-of-selection.
Extract open customer items from BSID
select bukrs kunnr gjahr belnr buzei budat bldat waers xblnr shkzg
 dmbtr zfbdt zbd1t zbd2t zbd3t rebzg rebzt
 from bsid
 into table it_bsadbsid
 where kunnr in s_kunnr
 and budat le p_datum.
Extracct cleared customer items from BSAD
select bukrs kunnr gjahr belnr buzei budat bldat waers xblnr shkzg
 dmbtr zfbdt zbd1t zbd2t zbd3t rebzg rebzt
 from bsad
 appending table it_bsadbsid
 where kunnr in s_kunnr
 and budat le p_datum
 and augdt ge p_datum.
Ensure that items were not selected twice while getting data from the
open and cleared items tables (Only if transaction occured during
report run).
sort it_bsadbsid by bukrs belnr gjahr buzei.
delete adjacent duplicates from it_bsadbsid
 comparing bukrs belnr gjahr buzei.
if it_bsadbsid[] is initial.
No data found for selection
 message s001(zgen).
 exit.
endif.
Merge data for report output
perform merge_data tables it_bsadbsid
 it_merged.
Build field catalog
perform build_field_catalog tables it_fieldcat.
Output report via ALV
perform output_report_via_alv tables it_fieldcat
 it_merged.
*& Form merge_data
 text
form merge_data tables pa_it_bsadbsid type ty_it_bsadbsid
 pa_it_merged type ty_it_merged.
Local work areas
data:
lwa_bsadbsid type ty_bsadbsid,
lwa_merged type ty_merged.
Local structures
data:
lst_faede like faede.
Local variables
data:
lva_daysover type i,
lva_merged_tabix like sy-tabix.
loop at pa_it_bsadbsid into lwa_bsadbsid.
Lookup merged entry for customer
 clear lwa_merged.
 read table pa_it_merged into lwa_merged
 with key kunnr = lwa_bsadbsid-kunnr
 binary search.
 lva_merged_tabix = sy-tabix.
 if sy-subrc ne 0.
 Create new merged record for customer
 lwa_merged-kunnr = lwa_bsadbsid-kunnr.
 Get customer details from KNA1
 clear kna1.
 select single *
 from kna1
 where kunnr eq lwa_bsadbsid-kunnr.
 Get customer address details from ADRC
 clear adrc.
 select single *
 from adrc
 where addrnumber eq kna1-adrnr
 and date_from le p_datum.
 lwa_merged-name1 = adrc-name1.
 lwa_merged-city1 = adrc-city1.
 lwa_merged-post_code1 = adrc-post_code1.
 lwa_merged-street = adrc-street.
 lwa_merged-house_num1 = adrc-house_num1.
 lwa_merged-tel_number = adrc-tel_number.
 lwa_merged-fax_number = adrc-fax_number.
 Get credit limit details from KNKK
 clear knkk.
 select single *
 from knkk
 where kunnr eq lwa_bsadbsid-kunnr
 and kkber eq p_kkber.
 lwa_merged-klimk = knkk-klimk.
 lwa_merged-skfor = knkk-skfor.
 Get customer contact person details from KNVK
 clear knvk.
 select single *
 from knvk
 where kunnr eq lwa_bsadbsid-kunnr
 and pafkt eq p_pafkt.
 lwa_merged-namev = knvk-namev.
 lwa_merged-namew = knvk-name1.
 lwa_merged-telf1 = knvk-telf1.
 insert lwa_merged into pa_it_merged index lva_merged_tabix.
 endif.
Interpret debit/credit indicator
 case lwa_bsadbsid-shkzg.
 when co_shkzg_h.
 Credit
 lwa_bsadbsid-dmbtr = 0 - lwa_bsadbsid-dmbtr.
 when co_shkzg_s.
 Debit
 endcase.
Perform ageing
 clear lst_faede.
 move-corresponding lwa_bsadbsid to lst_faede.
 lst_faede-koart = co_koart_d.
 call function 'DETERMINE_DUE_DATE'
 exporting
 i_faede = lst_faede
 importing
 e_faede = lst_faede
 exceptions
 others = 1.
 lva_daysover = p_datum - lst_faede-netdt.
Accumulate total.
 add lwa_bsadbsid-dmbtr to lwa_merged-total.
 if lva_daysover le rastbis1.
 add lwa_bsadbsid-dmbtr to lwa_merged-rast1.
 else.
 if lva_daysover le rastbis2 or
 rastbis3 is initial.
 add lwa_bsadbsid-dmbtr to lwa_merged-rast2.
 else.
 if lva_daysover le rastbis3 or
 rastbis4 is initial.
 add lwa_bsadbsid-dmbtr to lwa_merged-rast3.
 else.
 if lva_daysover le rastbis4 or
 rastbis5 is initial.
 add lwa_bsadbsid-dmbtr to lwa_merged-rast4.
 else.
 if lva_daysover le rastbis5.
 add lwa_bsadbsid-dmbtr to lwa_merged-rast5.
 else.
 add lwa_bsadbsid-dmbtr to lwa_merged-rast6.
 endif.
 endif.
 endif.
 endif.
 endif.
Update the merged record
 modify pa_it_merged from lwa_merged index lva_merged_tabix.
endloop.
endform. " merge_data
*& Form build_field_catalog
 text
form build_field_catalog tables pa_it_fieldcat type slis_t_fieldcat_alv.
Local work areas
data:
 lwa_fieldcat type slis_fieldcat_alv.
--WG1K903216: Start Insert-
data: v_datum type datum,
 v_mdmth type datum,
 v_datxt type string,
 v_noday type i.
--WG1K903216: End Insert---
refresh pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'KUNNR'.
lwa_fieldcat-ref_tabname = 'KNA1'.
lwa_fieldcat-ref_fieldname = 'KUNNR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '1'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'NAME1'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'NAME1'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '2'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'CITY1'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'CITY1'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '3'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'POST_CODE1'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'POST_CODE1'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '4'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'STREET'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'STREET'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '5'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'HOUSE_NUM1'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'HOUSE_NUM1'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '6'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'TEL_NUMBER'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'TEL_NUMBER'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '7'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'FAX_NUMBER'.
lwa_fieldcat-ref_tabname = 'ADRC'.
lwa_fieldcat-ref_fieldname = 'FAX_NUMBER'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '8'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'NAMEV'.
lwa_fieldcat-ref_tabname = 'KNVK'.
lwa_fieldcat-ref_fieldname = 'NAMEV'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '9'.
lwa_fieldcat-seltext_l = 'Contact first name'.
lwa_fieldcat-seltext_m = 'Contact Fname'.
lwa_fieldcat-seltext_s = 'Ctct Fname'.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'NAMEW'.
lwa_fieldcat-ref_tabname = 'KNVK'.
lwa_fieldcat-ref_fieldname = 'NAME1'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '10'.
lwa_fieldcat-seltext_l = 'Contact last name'.
lwa_fieldcat-seltext_m = 'Contact Lname'.
lwa_fieldcat-seltext_s = 'Ctxt Lname'.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'TELF1'.
lwa_fieldcat-ref_tabname = 'KNVK'.
lwa_fieldcat-ref_fieldname = 'TELF1'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '11'.
lwa_fieldcat-seltext_l = 'Contact phone no.'.
lwa_fieldcat-seltext_m = 'Contact phone'.
lwa_fieldcat-seltext_s = 'Ctct Phne'.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'KLIMK'.
lwa_fieldcat-ref_tabname = 'KNKK'.
lwa_fieldcat-ref_fieldname = 'KLIMK'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '12'.
lwa_fieldcat-seltext_l = 'Credit limit'.
lwa_fieldcat-seltext_m = 'Credit limit'.
lwa_fieldcat-seltext_s = 'Crdt limit'.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'SKFOR'.
lwa_fieldcat-ref_tabname = 'KNKK'.
lwa_fieldcat-ref_fieldname = 'SKFOR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '13'.
lwa_fieldcat-seltext_l = 'Credit used'.
lwa_fieldcat-seltext_m = 'Credit used'.
lwa_fieldcat-seltext_s = 'Crdt used'.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'TOTAL'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '14'.
lwa_fieldcat-seltext_l = 'Total'.
lwa_fieldcat-seltext_m = 'Total'.
lwa_fieldcat-seltext_s = 'Total'.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'RAST1'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '15'.
--WG1K903216: Start Delete-
concatenate '<'
 rastbis2
 into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Delete---
--WG1K903216: Start Insert-
clear: v_datum,
 v_datxt.
v_noday = rastbis2.
Always use the middle of the report month as a heading reference date.
concatenate p_datum+0(6) '15' into v_mdmth.
call function 'ZWAG_DATE_CALCULATOR'
 exporting i_datum = v_mdmth
 i_noday = v_noday
 i_oprnd = '+'
 importing e_datum = v_datum
 exceptions invalid_operand = 1.
call function 'ZWAG_END_MONTH'
 exporting i_datum = v_datum
 importing e_datum = v_datum
 e_datxt = v_datxt
 exceptions invalid_date = 1.
concatenate 'Due' v_datxt into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Insert---
lwa_fieldcat-seltext_m = lwa_fieldcat-seltext_l.
lwa_fieldcat-seltext_s = lwa_fieldcat-seltext_l.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'RAST2'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '16'.
--WG1K903216: Start Delete-
concatenate rastbis1
 rastbis2
 into lwa_fieldcat-seltext_l
 separated by co_delim_dash.
--WG1K903216: End Delete---
--WG1K903216: Start Insert-
clear: v_datum,
 v_datxt.
v_noday = rastbis1.
call function 'ZWAG_DATE_CALCULATOR'
 exporting i_datum = v_mdmth
 i_noday = v_noday
 i_oprnd = '+'
 importing e_datum = v_datum
 exceptions invalid_operand = 1.
call function 'ZWAG_END_MONTH'
 exporting i_datum = v_datum
 importing e_datum = v_datum
 e_datxt = v_datxt
 exceptions invalid_date = 1.
concatenate 'Due' v_datxt into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Insert---
lwa_fieldcat-seltext_m = lwa_fieldcat-seltext_l.
lwa_fieldcat-seltext_s = lwa_fieldcat-seltext_l.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'RAST3'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '17'.
--WG1K903216: Start Delete-
concatenate rastbis2
 rastbis3
 into lwa_fieldcat-seltext_l
 separated by co_delim_dash.
--WG1K903216: End Delete---
--WG1K903216: Start Insert-
clear: v_datum,
 v_datxt.
v_noday = rastbis2.
call function 'ZWAG_DATE_CALCULATOR'
 exporting i_datum = v_mdmth
 i_noday = v_noday
 i_oprnd = '-'
 importing e_datum = v_datum
 exceptions invalid_operand = 1.
call function 'ZWAG_END_MONTH'
 exporting i_datum = v_datum
 importing e_datum = v_datum
 e_datxt = v_datxt
 exceptions invalid_date = 1.
concatenate 'Due' v_datxt into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Insert---
lwa_fieldcat-seltext_m = lwa_fieldcat-seltext_l.
lwa_fieldcat-seltext_s = lwa_fieldcat-seltext_l.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'RAST4'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '18'.
--WG1K903216: Start Delete-
concatenate rastbis3
 rastbis4
 into lwa_fieldcat-seltext_l
 separated by co_delim_dash.
--WG1K903216: End Delete---
--WG1K903216: Start Insert-
clear: v_datum,
 v_datxt.
v_noday = rastbis3.
call function 'ZWAG_DATE_CALCULATOR'
 exporting i_datum = v_mdmth
 i_noday = v_noday
 i_oprnd = '-'
 importing e_datum = v_datum
 exceptions invalid_operand = 1.
call function 'ZWAG_END_MONTH'
 exporting i_datum = v_datum
 importing e_datum = v_datum
 e_datxt = v_datxt
 exceptions invalid_date = 1.
concatenate 'Due' v_datxt into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Insert---
lwa_fieldcat-seltext_m = lwa_fieldcat-seltext_l.
lwa_fieldcat-seltext_s = lwa_fieldcat-seltext_l.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'RAST5'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '19'.
--WG1K903216: Start Delete-
concatenate rastbis4
 rastbis5
 into lwa_fieldcat-seltext_l
 separated by co_delim_dash.
--WG1K903216: End Delete---
--WG1K903216: Start Insert-
clear: v_datum,
 v_datxt.
v_noday = rastbis4.
call function 'ZWAG_DATE_CALCULATOR'
 exporting i_datum = v_mdmth
 i_noday = v_noday
 i_oprnd = '-'
 importing e_datum = v_datum
 exceptions invalid_operand = 1.
call function 'ZWAG_END_MONTH'
 exporting i_datum = v_datum
 importing e_datum = v_datum
 e_datxt = v_datxt
 exceptions invalid_date = 1.
concatenate 'Due' v_datxt into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Insert---
lwa_fieldcat-seltext_m = lwa_fieldcat-seltext_l.
lwa_fieldcat-seltext_s = lwa_fieldcat-seltext_l.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
clear lwa_fieldcat.
lwa_fieldcat-tabname = 'PA_IT_MERGED'.
lwa_fieldcat-fieldname = 'RAST6'.
lwa_fieldcat-ref_tabname = 'BSAD'.
lwa_fieldcat-ref_fieldname = 'DMBTR'.
lwa_fieldcat-row_pos = '1'.
lwa_fieldcat-col_pos = '20'.
--WG1K903216: Start Delete-
concatenate '>'
 rastbis5
 into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Delete---
--WG1K903216: Start Insert-
clear: v_datum,
 v_datxt.
v_noday = rastbis5.
call function 'ZWAG_DATE_CALCULATOR'
 exporting i_datum = v_mdmth
 i_noday = v_noday
 i_oprnd = '-'
 importing e_datum = v_datum
 exceptions invalid_operand = 1.
call function 'ZWAG_END_MONTH'
 exporting i_datum = v_datum
 importing e_datum = v_datum
 e_datxt = v_datxt
 exceptions invalid_date = 1.
concatenate 'Due By' v_datxt into lwa_fieldcat-seltext_l
 separated by space.
--WG1K903216: End Insert---
lwa_fieldcat-seltext_m = lwa_fieldcat-seltext_l.
lwa_fieldcat-seltext_s = lwa_fieldcat-seltext_l.
lwa_fieldcat-ddictxt = 'L'.
append lwa_fieldcat to pa_it_fieldcat.
endform. " build_field_catalog
*& Form output_report_via_alv
 text
form output_report_via_alv
 tables pa_it_fieldcat type slis_t_fieldcat_alv
 pa_it_merged type ty_it_merged.
Local variables
data:
 lva_repid like sy-repid,
 lva_formname type slis_formname.
lva_repid = sy-repid.
lva_formname = 'USER_COMMAND'.
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = lva_repid
 i_callback_user_command = lva_formname
 i_save = 'A'
 is_variant = st_variant
 it_fieldcat = pa_it_fieldcat[]
 tables
 t_outtab = pa_it_merged
 exceptions
 program_error = 1
 others = 2.
endform. " output_report_via_alv

Hi shiva
Thanks for your help,
Can you check this coding and revert me back ASAP Please.
REPORT BDS_GOS_CONNECTION.
DATA : logical_system LIKE BAPIBDS01-log_system.
 CLASSNAME LIKE BAPIBDS01-CLASSNAME
 OBJKEY LIKE SWOTOBJID-objkey.
PARAMETERS: pa_lo_sys BAPIBDS01-log_system,
 pa_class like BPIBDS01-CLASSNAME,
 pa_objkey like swotobjidobjkey.
AT SELECTION-SCREEN.
CALL FUNCTION 'BDS_GOS_CONNECTIONS_GET'
 EXPORTING
 bor_id = bor_id
 IMPORTING
 logical_sytem = pa_lo_sys.
 classname = pa_class.
 objkey = pa_objkey.
 EXCEPTIONS
 no_objects_found = 1
 internal_error = 2
 internal_gos_error = 3.
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
clear v_attno1.
i_object1-typeid = 'BUS2012'.
i_object1-catid = 'BO'.
i_object1-instid = i_yItem-docno.
call method cl_gos_attachment_query=>count_for_object
 exporting
 is_object = i_object1
 ip_arl = space
 receiving
 rt_stat = i_stat1.
read table i_stat1 into wa_stat1 index 1.
if sy-subrc eq c_0.
 move wa_stat1-counter to v_attno1.
endif.
CALL METHOD cl_gos_attachment_query=>count_for_object
EXPORTING
is_object = object
ip_arl = space
RECEIVING
rt_stat = lt_stat.
READ TABLE lt_stat INDEX 1 into ls_stat.
count = ls_stat-counter.
*The object has to be a concatenation of your document, like this:
CONCATENATE object-instid tab-gjahr INTO object-instid.
ELSE.
CONCATENATE tab-bukrs tab-belnr tab-gjahr INTO
object-instid.
ENDIF.

Function Module to Release Scheduled Jobs

Dear All,
I have a requirement to create all the background jobs in SCHEDULED status, this is achieved by using the function modules JOB_OPEN, JOB_SUBMIT and JOB_CLOSE.
Now at a later point of time, i want to release only a few jobs, which were created using the above mentioned procedure. Insead of doing it manually, is there any way to automate this step ??
Regards,
kartik

Dear Mr. Parupalli,
That solved my problem. Thank you.
Regards,
kartik

Call RFC Function Module and return 1000 records at a time

I would like to call a Remote Enabled Function Module from a non SAP system. This function module will select data from the database and return it to the calling program.
Suppose there are 100,000 records that need to be returned, but the calling module would like the data in chunks of 1000 records. Therefore the calling program would call the FM 100 times.
How do I code the function module to know on each subsequent call to grab the next chunk of 1000 records?
Let me know if additional information is needed.
Thanks,
Aaron

Hello,
Here is how you can go for this issue:
1. Create one RFC function module with following parameter. These parameters are with respective of chunking logic.
     Import: Package Size
     Export: Total number of records
     Changing: chunk count
Implement following logic:
1. First of you need to know how many chunks you need to fetch for that get the count of total number of records. This is one
    time activity so you better maintain one flag import parameter will be set to 'X' only first call.
2. Get the number of chunk using total number of records / chunk size for e.g. 1000 / 100 so chunk count = 10.
3. Define internal chunk counter in function module which will be used to locate the correct chunk depending on the chunk
    counter value sent from calling program.
4. Send first call with package size 100 and chunk count = 1, execute select statement and increment internal
    chunk count check if chunk count = internal chunk count in current case chunk count = 1 so exit select statement and return
    with first chunk.
5. Send second call with package size 100 and chunk count = 2. Execute select statement and check chunk count with internal
    chunk counter, in current case it will be 1 so skip that data and go for next chunk of 100 records increment internal chunk
    counter. In this case it will match with external chunk count = 2. load output table with that data and return to calling program.
6. Repeat step 4 until you reach last chunk.
You need to use SELECT...ENDSELECT with PACKAGE SIZE addition so for every loop it will return number of records mentioned in package size.
Hope this helps.
Thanks,
Augustin.

Error while passing a table to a function module

Hi Iam passing a table g_tab of length 376 flat structure to the function module..under TABLES section parameter.
Changedocument_read_headers.
iam getting a complile time error like the below displayed thing. Can u tell me how to solve this ?
In the function module interface, you can specify only
fields of a specific type and length under "I_CDHDR".
Although the currently specified field
"G_CDHDR_TAB" is the correct type, its length is incorrect.
Edited by: kiran kumar on Jul 7, 2008 8:53 AM

probably u making a mistake while declaring the table
declare it like this in the tables section:
S_JOB LIKE RNGE_OBJID
where s_job is the internal table name and RANGE_OBJID is a structure type and NOT an internal table type.

RFC Error While Invoking A Remote Function Module.

I am invoking A remote function module while invoking it get an exception when i see the error logs
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Screen output without connection to user. , error key: RFC_ERROR_SYSTEM_FAILURE at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101) at... [see details]
can anyone pls tell me what the error is..
regards
Nilesh Taunk.

Hi Nilesh Taunk,
You can go through the following steps
-o JCO Exceptions 1. http://help.sap.com/saphelp_nw04s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
-o JCO Exceptions 2. http://help.sap.com/saphelp_nw04/helpdata/en/f6/e002416225f023e10000000a155106/frameset.htm
-o Restart of the J2EE instance and try re-importing the RFC model. Sometimes it helps.
-o Logon into WebDynpro Content Administrator as a J2EE Admin and check if the JCO Connections and User /pwd of your application is correct. You can ping or test your JCO connections. if something is wrong, enter the values again for JCO n retest them.
-o Try undeploying or removing the complete application and redeploy it.
Tu undeploy please go to
Go to Visual Admin -> Server -> Services -> Deploy ->

Under Runtime Tab
select the server, open the tree , you would find the webdypro list there.
Now select an application, first stop it, remove it and redeploy if necessary.
Let us know if you could solve the problem or not, gud luck!
Rgds,
Sreenivas.

Error while generating Web Service from a function module.

Hi Experts,
I am trying to create a web service from function module by doing the steps as mentioned in the below document:
http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417800)ID1146834250DB10778842957931285337End?rid=/library/uuid/80fa3dff-ce76-2a10-3f94-f3df8f2db5a2&overridelayout=true
When i save it as an local object instead of generating the Web Service it gives me the below error:
"Error during activation of Web Service"
Kindly let me know what needs to be done inorder to resolve this issue.
I have a feeling that this error may be with respect to some authorizations, in that case how do we resolve it
Helpful Inputs Awaited.!!!
Thanks
Dhwani

Hi Dhawani,
Hi Pavan,
Can you please elaborate...how this will help??
Thanks
Dhwani
I dont know the specific reason but internally there may some inconsistancy but i faced the same error and i tried with saving it in the package.
Thanks

CNTL_ERROR while calling a function module from Java webdynpro

I am calling a RFC function module from javawebdynpro app
which inturn calls a function module performing BDC on CAPP transaction. When I run this from SE37 of the same system or a different system everything works fine. But when called from Java webdynpro app, it raises a CNTL_ERROR exception and creates a short dump.
Any help on this is highly appreciated

Good catch, BI Learner. This was exactly it: when assigning the values from SOURCEFIELDS directly to the import/export parameters, you have to make sure that the types are EXACTLY the same, otherwise it will not work (the routine stops with an error when calling the FM, but there is no dump).
Therefore, to solve my problem, I created the declarations precisely as expected by the FM and assigned the values to these fields:
DATA:
      SOURCEVAL TYPE /BIC/OIINVQTY,
      SOURCEUOM TYPE /BIC/OIUSUOM,
      USITM TYPE /BIC/OIUSITM,
      TARGETUOM TYPE /BIC/OIUSUOM,
      CONVERTED_COST TYPE /BIC/OIINVQTY.
DATA PRODUCTION_UOM TYPE /BIC/OIUSUOM.
" get the Production UOM
    SELECT SINGLE I~/BIC/USPRDUOM
      FROM /BIC/PUSITM AS I
      INTO PRODUCTION_UOM
      WHERE I~/BIC/USITM = SOURCE_FIELDS-/BIC/USITM AND I~OBJVERS = 'A'.
    IF ( SY-SUBRC = 4 ). " no records found
      "RAISE PARTNO_NOT_FOUND.
      RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
    ENDIF.
" load the parameters
    SOURCEVAL = SOURCE_FIELDS-/BIC/USFRZMFC.
    SOURCEUOM = SOURCE_FIELDS-BASE_UOM.
    USITM = SOURCE_FIELDS-/BIC/USITM.
" then you can call the FM
    CALL FUNCTION 'Z_CA_CONVERT_US_COST'
      EXPORTING
        PSOURCEVAL                = SOURCEVAL
        PSOURCEUOM                = SOURCEUOM
        PUSITM                    = USITM
        PTARGETUOM                = PRODUCTION_UOM
      IMPORTING
        PTARGETVAL                = CONVERTED_COST
      EXCEPTIONS
        CONVERSION_NOT_MAINTAINED = 1
        PARTNO_NOT_FOUND          = 2
        OTHERS                    = 3.
" ... [do the rest]
Thanks for your help,
Dennis

Salesorder function module

Similar Messages

Maybe you are looking for