USER EXISTS - Very Useful

Exit Name Description

SDTRM001 Reschedule schedule lines without a new ATP check

V45A0002 Predefine sold-to party in sales document

V45A0003 Collector for customer function modulpool MV45A

V45A0004 Copy packing proposal

V45E0001 Update the purchase order from the sales order

V45E0002 Data transfer in procurement elements (PRreq., assembly)

V45L0001 SD component supplier processing (customer enhancements)

V45P0001 SD customer function for cross-company code sales

V45S0001 Update sales document from configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0004 Effectivity type in sales order

V45W0001 SD Service Management: Forward Contract Data to Item

V46H0001 SD Customer functions for resource-related billing

V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

V45A0001 Determine alternative materials for product selection

SDVFX007 User exit: Billing plan during transfer to Accounting

SDVFX008 User exit: Processing of transfer structures SD-FI

SDVFX009 Billing doc. processing KIDONO (payment reference number)

SDVFX010 User exit item table for the customer lines

SDVFX011 Userexit for the komkcv- and kompcv-structures

V05I0001 User exits for billing index

V05N0001 User Exits for Printing Billing Docs. using POR Procedure

V60A0001 Customer functions in the billing document

V60P0001 Data provision for additional fields for display in lists

V61A0001 Customer enhancement: Pricing

MV45AFZ4 User exits

MV45AFZA

MV45AFZB User Exits

MV45AFZB_USEREXIT_CHECK_VBAK

MV45AFZB_USEREXIT_FILL_VBAP_FR

MV45AFZC User Exits

MV45AFZD

MV45AFZF

MV45AFZH

MV45AFZU

MV45AFZZ

MV45AFZZ_FCODE_KKON_REDIRECT

MV45AFZZ_FCODE_PKON_REDIRECT

MV45AFZZ_USEREXIT_FIELD_MODIFI

read more...

SAP Transactions & Programs

search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.

EDI Specific Transactions
VOE1 Translation between EDI categories and SD item categories

VOE2 Table EDSC view. Customer link to sales area detail

VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc

VOE4 Table view EDPAR. Link external partner number with our internal number

WEDI EDI Administrator Menu

BALE Idoc Administration

Scheduling agreements
OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.

OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.

OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.

IDoc Transactions
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.

WE05 View IDocs

WE19 EDI test tool. Use to test inbound Function module changes.

WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing

WE30 Create IDoc extension type

WE31 Segment create

WE57 Assign function module to logical message and IDoc type

WE60 IDoc type documentation tool

WE82 Link Release detail to Extension IDoc Type

BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations

BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)

BALA ALE Application Distribution

BALM ALE Master Data Distribution

Output determination
856 - ASN
V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments

VV21,VV22,VV23 Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21

VL71 Reissue output for deliveries

810 - Invoice
V/54 Maintain access sequence for billing documents

VV31,VV32,VV33 Create condition records for billing documents. (RD00 – RE Billing party)

VF31 Reissue output for billing documents

855 – Order Response
V/30 Sales document output types (BA00)

V/48, V/32, V/43 Maintain access sequence for sales documents

VV11,VV12,VV13 Create condition records for sales documents. (BA00 – SP Sold to party)

Requirements coding
V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.

Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
VA02 Sales order change

VA05 List of sales orders

VA22 Quotation change

VA32 Scheduling agreement change

VA42 Contract change

Billing
VF02 Change billing document

VF11 Cancel Billing document

VF04 Billing due list

FBL5N Display Customer invoices by line

FBL1N Display Vendor invoices by line

Delivery
VL02N Change delivery document

VL04 Delivery due list

VKM5 List of deliveries

VL06G List of outbound deliveries for goods issue

VL06P List of outbound deliveries for picking

VL09 Cancel goods issue

VT02N Change shipment

VT70 Output for shipments

General
VKM3, VKM4 List of sales documents

VKM1 List of blocked SD documents

VD52 Material Determination

Workflow
SWEAD Event queue administration

SWE2 Event type linkages

SWE3 Event linkages

PPOME Organizational Unit Maintenance

SWE5 Consistency Checks for Event Linkages

SWUD Workflow Diagnostic Tool

General
The following section provides detail on other useful SAP areas.

Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.

VL04 Delivery due list. Run the delivery due with your order number to create the delivery

LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save

The Transfer order should now be saved. It now needs to be confirmed.

In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
Enter
Save
The transfer order is now confirmed.

VL02N Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit

Purchase Orders
ME22N PO Change

ME57 Create PO from purchase requisition

ATP
CO09 Availability overview

Goods Movement
MIGO Post goods receipt

MB51 Material document list

MB01 Goods Movement

Other
MD04 Material Requirements. Shows material requirements and releases against materials

SE38 ABAP Editor. Used to modify ABAP programs

SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available

SHDB Transaction recorder (BDC)

CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work

SE16 Table contents display

SOST View mails sent externally from SAP

SU53 Check authorization object

SQVI Table Quickviewer – Used to created quick client dependent reports

ST22 ABAP Dump Analysis

ST01 System trace

ST11 Display developer trace

ST05 SQL Trace

SM21 System log

ST22 Display short dumps

SM12 Display locked entries

Programs
List of ABAP Reports

Idoc
RBDAPP01 Post inbound Idocs to application documents

RBDAGAI2 Re-processing of IDocs after ALE input error

RBDAGAIE Reprocessing of edited IDocs

RBDMANIN Start error handling for non-posted Idocs

RSEINB00 Idoc inbound processing by file

RSEOUT00 Process outbound IDocs

General
RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.

RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status’ sent from SAP.

RHSOBJCH Corrects the following error in workflow customizing:

Transport object PDST

Information Table SOBJ is consistent as regards key tables

***Error*** Table HRP1600 Not an entry in table SOBJ

Information Table SOBJ is consistent as regards PAD tables

See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.

RSPO0075 Run report RSPO0075 to activate access method M for device types.

read more...

How To Do Configuration For Credit Management

Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.

An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.

For example, if your credit management is centralized, you can define one credit control area for all of your company codes.

If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.

Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.

read more...

Understanding BADI

DEFINING THE BADI

1) execute Tcode SE18.
2) Specify a definition Name : ZBADI_SPFLI
3) Press create
4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
multiple use.
5) Choose the interface tab
6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
7) Dbl clk on interface name to start class builder . specify a method name (name,
level, desc).

Method level desc
Linese;ection instance methos some desc

8) place the cursor on the method name desc its parameters to define the interface.
Parameter type refe field desc
I_carrid import spfli-carrid some
I_connid import spefi-connid some

9) save , check and activate…adapter class proposed by system is
ZCL_IM_IM_LINESEL is genereated.


IMPLEMENTATION OF BADI DEFINITION

1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
2) Specify aname for implementation ZIM_LINESEL
3) Specify short desc.
4) Choose interface tab. System proposes a name fo the implementation class.
ZCL_IM_IMLINESEL which is already generarted.
5) Specify short desc for method
6) Dbl clk on method to insert code..(check the code in “AAA”).
7) Save , check and activate the code.


Now write a sample program to use this badi method..
Look for “BBB” sample program.


“AAA”

data : wa_flights type sflight,
it_flights type table of sflight.

format color col_heading.
write:/ 'Flight info of:', i_carrid, i_connid.
format color col_normal.

select * from sflight
into corresponding fields of table it_flights
where carrid = i_carrid
and connid = i_connid.

loop at it_flights into wa_flights.
write:/ wa_flights-fldate,
wa_flights-planetype,
wa_flights-price currency wa_flights-currency,
wa_flights-seatsmax,
wa_flights-seatsocc.
endloop.



“BBB”

*&---------------------------------------------------------------------*
*& Report ZBADI_TEST *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*

REPORT ZBADI_TEST .

tables: spfli.

data: wa_spfli type spfli,
it_spfli type table of spfli with key carrid connid.

*Initialise the object of the interface.
data: exit_ref type ref to ZCL_IM_IM_LINESEL,
exit_ref1 type ref to ZIF_EX_BADISPFLI1.

selection-screen begin of block b1.
select-options: s_carr for spfli-carrid.
selection-screen end of block b1.

start-of-selection.
select * from spfli into corresponding fields of table it_spfli
where carrid in s_carr.

end-of-selection.
loop at it_spfli into wa_spfli.
write:/ wa_spfli-carrid,
wa_spfli-connid,
wa_spfli-cityfrom,
wa_spfli-deptime,
wa_spfli-arrtime.

hide: wa_spfli-carrid, wa_spfli-connid.

endloop.


at line-selection.
check not wa_spfli-carrid is initial.
create object exit_ref.
exit_ref1 = exit_ref.

call method exit_ref1->lineselection
EXPORTING
i_carrid = wa_spfli-carrid
i_connid = wa_spfli-connid.

clear wa_spfli.

read more...

SAP BAdI Introduction

BADI - Business Add Ins are enhancements to the standard version of the code of SAP. They can be inserted into the SAP system to accommodate user requirements too specific to be included in the standard delivery. Customers can find the possible enhancements (BADIs) in their SAP system in the Implementation Guide (IMG) and in the component hierarchy. BADI definitions are included in the IMG so that the customer can create suitable, company-specific implementations. SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces.

Two different views are available:



* In the definition view, an application programmer defines exit points in a source that allow specific industry sectors, partners, and customers to attach additional coding to standard SAP source code without having to modify the original object.
* In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard solution if one is available.


Definition of A BAdI



SAP application developer actually defines a Business Add-In available to an application program. Tcode SE18 can also be used to see the definition of existing badi .The following are the steps in defining a BADI:

1. Using the SAP BADI builder, the SAP application developer defines an enhancement (BADI). It consists of an interface with a method.
2. The interface name is generated automatically and can be changed. The system branches to the Class Builder.
3. Using the Class Builder, the developer assigns a method to the interface.
4. For each method, he defines parameters. Parameters can either be importing or changing and these are the fields available for customer to use for enhancements. Importing parameters are the fields being passed from the calling program and changing parameters are the fields being passed back to the program.
5. The Business Add-In is then activated in the Class Builder.

Note: Documentation of the BADI usually provides the list of parameters and their definition. For example, for method DETERMINE_EXTPO, the available parameters are:
Importing
o ITEM_DATA Item data (is a structure)
Changing
o BBP_EXTPO_GL
o If the field has the value X, the request is subject to the extended classic scenario.
o If the field is empty, the request is not subject to the extended classic scenario.

Implementation of a BAdI

If a customer wishes to use a Business Add-In, he or she first creates an implementation. The customer must implement the methods and the enhancements. You need to program the interface method in such a way that, when the add-in is called from the application program, it will perform the specific action the customer intends. The following are the steps customer can follow in implementing a BADI:
1. In the SAP menu, choose ABAP Workbench ® Utilities ® Business Add-Ins (transaction SE19) or double-click the corresponding activity in the Implementation Guide (IMG).

2. Enter a name for the implementation and then click the Create pushbutton.
3. Enter the name of the add-in for which you want to create an implementation for in the dialog box that appears. Choose the Interface tab.
4. Choose ABAP Code as the implementation type.
5. Navigate to the Class Builder by double-clicking the method. You must first enter a
package before the Class Builder is displayed.
6. Insert the desired source code for the implementation between the method if_ex_businessaddin~method. and endmethod (statements that already exist) You need to use the parameters (importing and changing) as fields within the BADI. You can define additional fields you need in the coding as local data fields.
7. Save your entries and return to the Change Implementation screen.
8. Choose Activate. The enhancement’s active components are then called at runtime.

EXAMPLE (code)

Definition name BBP_EXTLOCALPO_BADI

Implementation Name ZEXTENDEDCLASSIC

Interface name IF_EX_BBP_EXTLOCALPO_BADI
Name of implementing class: ZCL_IM_EXTENDEDCLASSIC

Method DETERMINE_EXTPO
ABAP Code Determination of Control for Extended

read more...

Certification - Solution Consultant

Click read more to view the full content

SAP Consultant Certification - ERP Operations

Certification - Solution Consultant

Certificate Name	Exam Topics	Duration (h)/ No. of questions	Software Components	Curriculum	Booking Code (SAP internal)
SCM - WM & LE with mySAP ERP 2005	German/English	3 / 80	SAP ECC 6.0		C_TSCM66_05
SCM - Procurement with mySAP ERP 2005	German/English	3 / 80	SAP ECC 6.0	English/German	C_TSCM52_05
SCM - Order Fulfillment with mySAP ERP 2004	German/English	3 / 80	SAP ECC 5.0	English/German	C_TSCM64_04
SCM - Procurement with mySAP ERP (2004)	German/English	3 / 80	SAP ECC 5.0	English/German	C_TSCM54_04
mySAP SCM - Order Fulfillment (2003)	German/English	3 / 80	SAP R/3 Enterprise	English	C_TSCM64_03
mySAP SCM - Procurement (2003)	German/English	3 / 80	SAP R/3 Enterprise	English	C_TSCM54_03

read more...

SAP ERP Operations certification

SAP Consultant Certification - ERP Operations

Certification - Solution Consultant

Certificate Name	Exam Topics	Duration (h)/ No. of questions	Software Components	Curriculum	Booking Code (SAP internal)
SCM - WM & LE with mySAP ERP 2005	German/English	3 / 80	SAP ECC 6.0		C_TSCM66_05
SCM - Procurement with mySAP ERP 2005	German/English	3 / 80	SAP ECC 6.0	English/German	C_TSCM52_05
SCM - Order Fulfillment with mySAP ERP 2004	German/English	3 / 80	SAP ECC 5.0	English/German	C_TSCM64_04
SCM - Procurement with mySAP ERP (2004)	German/English	3 / 80	SAP ECC 5.0	English/German	C_TSCM54_04
mySAP SCM - Order Fulfillment (2003)	German/English	3 / 80	SAP R/3 Enterprise	English	C_TSCM64_03
mySAP SCM - Procurement (2003)	German/English	3 / 80	SAP R/3 Enterprise	English	C_TSCM54_03

read more...