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...

Setup FI Fiscal Year Period

The client wants fiscal year to be set from May 1 – April 30 but they use a 4,4,5 accounting period setup meaning that every month end on the last Friday of the month. I am setting for 2006-2007. As you know, the FYV should be year dependent, so how can the periods be set up.

In IMG go to financial accounting global setting then go to fiscal year variant and set the fiscal year variant on year dependent year and follow the following procedure:

1. enter name of month started from may and end on april
2. enter the number of days in a month you want to close for example in may number of days is 28 instead of 31
3. enter period from 01 to 12 started from may to april
4. enter -1 against the month from jan to april

For Example :

Month Number of Days Period Year Shift
May06 28 01 0
June 35 02 0
July 28 03 0
Aug 28 04 0
Sep 35 05 0
Oct 28 06 0
Nov 28 07 0
Dec 35 08 0
Jan07 28 09 -1
Feb 28 10 -1
Mar 35 11 -1
Apr 31 12 -1

read more...

Check List for FI Year End Closing

Check List for FI Year End Closing


Click here to Get your Free SAP Magazine Now!

A D V E R T I S E M E N T

--------------------------------------------------------------------------------



Share the Experience and Exchange Ideas


HOME >> FINANCIAL MODULES >> CHECK LIST FOR FI YEAR

Discussion Center
Discuss
Query
Feedback/Suggestion
Yahoo Groups
Sirfdosti Groups
Contact Us

Check List for FI Year End Closing
1 Execute Report for InterCompany Activity & Journal Entries
2 Open posting period for next yr
3 Run Business Area's Assignment report.
4 Review list of recurring journal entries
5 Execute Recurring Entries for A/R, A/P, G/L
6 Process Parked A/R, A/P, G/L accounting documents
7 Final Cutoff for the Maintenance of Fixed Asset- Add Transfer and Retire
8 Run Depreciation in Test Run and post
9 Verify Display Log for Depreciation Test Run
10 Capitalize AUC Assets if needed
11 Enter Payroll Data to SAP
12 Verify Depreciation Balances with GL balances
13 Post Depreciation
14 Execute Asset History Report, and retire assets if needed
15 Adjust specific depreciation areas if necessary
16 Reconcile AM subledger with GL
17 Check Bank Data
18 Review AR Open Items
19 Review AP Open Items
20 Execute Pending Invoices


21 Clear Open Item for GRIR, freight
22 Reconciliation of Financial Documents and transactional figures
23 Open new CO Posting Period
24 Compare current (cost estimates) with last current price (Moving Avg)
25 Update current cost price to material master price field.
26 Process Freight charges, Match SD freight to actual
27 Review Internal Order Postings
28 Settle All Orders
29 Verify All Post Goods Issue have been Invoiced (Billing Due List)
30 Review SD Billng Doc from prior mth that have not yet been released to accounting
31 Reconciliation of MM movements in Transit Intra-SAP to NonSAP
32 Reconcile PI Inventory with SAP
33 Perform Manual Adjustment if needed
34 Verify balance of the GR/IR account
35 Post Accruals and Deferrals
36 Clearing of Cancelled Documents
37 Check Profitability Segment Adjustment
38 Aging Report-Reconcile GL balances with subledger balances AP
39 Check the check run numbers
40 Bank reconciliation Data
41 Enter Tax Journal Entry
42 Reconcile GL balances with subledger balances AR/MM/AP
43 Display Balance Sheet Adjustments
44 Post Balance Sheet Adjustments
45 Post Foreign Currency Valuation (foreign exchange)
46 Check generic cost centers for posting with wrong accounts
47 Correct wrong postings on generic cost centers
48 Check Validation dates for Cost Centers, Cost Elements, CO area
49 Check COGI--for both month end and year end
50 Doubtful receiviables
51 Verify In-transist Inventory
52 Reconcile PA to G/L
53 Post Cost Centre Assessments and Distributions
54 Run CO-FI Reconciliation to balance
55 Run BW reports P&L and Balance Sheet
56 Maintain CO yr variant
57 Fiscal Yr Balance carryforward AP/AR/AM
58 Fiscal Yr Balance carryforward CO
59 Fiscal Yr balance carryforward FI
60 Fiscal Yr balance carryforward PCA
61 Set Document number ranges - FI - new year
62 Set Document number ranges AP/AR - new year
63 Generate Financial statement Reports
64 Change Fiscal Year For Assets
65 Year end Closing-- Asset Accounting--final for year end
66 Close CO Posting Period
67 Close Prior A/R Posting Period
68 Close Prior A/P Posting Period
69 Close Prior MM Posting Period
70 Reverse accruals and deferrals for the new month
71 Reconciliation of Financial Documents from old fiscal year and new fiscal year
72 Load Balances, Budget Data for Cost centers, sales
73 Update Retained Earning Account , balance carry fwd

read more...