SAP FICO ACCOUNTS PAYABLE Issue-25

Issue No.: 25
The user has executed transaction code F110 to pay 50 vendors, but he only has 20 checks left. Hence, when he ran the program, it printed the checks with random numbers. Now the problem is he is unable to cancel the payments, as there is no check number. How can he reprint or cancel the checks?

The check printing program generated more checks than there are available check numbers. To handle this issue, follow these steps:

1. Before proceeding, ensure that you have maintained a new check lot through transaction code FCHI. Be sure to correct your check lot before you do anything.
2. In transaction code F110, enter the payment run ID and payment run date.
3. Go to the Printout/data medium tab and place the mouse curser on variant field against print program.
4. From the system menu, choose Environment → Maintain Variants

Figure Using transaction code F110

5. SAP R/3 will show the Maintain variant: XXXX screen, at the bottom of which you will see the section shown in Figure

Figure Using transaction code F110

6. Select Void and reprint checks from payment run already printed. This procedure will void all of the checks
generated through this particular payment program.
If you want to void and regenerate a particular set of checks, enter the check numbers you want to void along with a  void reason code.
7. Save the variant and come back to the payment run screen. Click on to

  generate the desired checks.

SAP FICO ACCOUNTS PAYABLE Issue-24

Issue No.: 24
In transaction code F-33 (bills of exchange discounting), the user entered all data. When this is executed, the user receives a message that A/C No. 400400 (Interest account) requires an assignment to a CO object. What does this mean?

When a controlling area is active, the user has to assign a valid cost object while posting expenses. In this case, bank interest is an expenses account, while posting selects a valid cost object.

SAP FICO ACCOUNTS PAYABLE Issue-23

Issue No.: 23
While posting a transaction through T-code F-58, the user sees this error message: "Changes for vendor XXXXXX not yet confirmed."

In SAP R/3 configuration, you define certain fields as sensitive to have proper control and tracking on master data changes. If the user changes these sensitive field(s), someone other than the user who changed the master data has to confirm these changes. Until such confirmation, the SAP R/3 system does not allow any transactions with that trading partner. For example, you configure payment term as a sensitive field. To accommodate business requirements, user XXXXX updates the payment term with a new payment term ID. In order to carry out any transactions with this business partner, the changes have to be approved by another user.

To confirm this change, the user has to use transaction code FK09. Follow this procedure before executing
transaction code F-58.

Maintain Accounting Configuration : Posting Keys List

Maintain Accounting Configuration : Posting Keys List
Posting keys	Name	Debit\Credit	Account Types
1	Invoice	Debit	Customer
2	Reverse Credit Memo	Debit	Customer
3	Bank Charges	Debit	Asset
4	Other Receivables	Debit	Customer
5	Outgoing payment	Debit	Customer
6	Payment Difference	Debit	Customer
7	Other Clearing	Debit	Customer
8	Payment Clearing	Debit	G\L Account
9	SPL G\L Debit	Debit	Customer
10	G\L postings	Debit	G\L Account
11	Credit Memo	Credit	Customer
12	Reserve Invoice	Credit	Customer
13	Reserve Charges	Credit	Customer
14	Other Payables	Credit	Vendor
15	Incoming payment	Credit	Customer
16	Payment Difference	Credit	Asset
17	Other Clearing	Credit	Customer
18	Payment Clearing	Credit	Customer
19	SPL G\L Credit	Credit	Customer
21	Credit Memo	Debit	Vendor
22	Reverse Invoice	Debit	Vendor
24	Other Receivables	Debit	Vendor
25	Outgoing payment	Debit	Vendor
26	Payment Difference	Debit	Vendor
27	Clearing	Debit	Vendor
28	Payment Clearing	Debit	Vendor
29	SPL G\L Debit	Debit	Vendor
31	Invoice	Credit	Vendor
32	Reverse Credit Memo	Credit	Vendor
34	Other Payables	Credit	Vendor
35	Incoming payment	Credit	Vendor
36	Payment Difference	Credit	Vendor
37	Other Clearing	Credit	Vendor
38	Payment Clearing	Credit	Asset
39	SPL G\L Credit	Credit	Vendor
40	Debit Entry	Debit	G\L Account
50	Credit Entry	Credit	G\L Account
70	Debit Asset	Debit	Asset
75	Credit Asset	Credit	Asset
80	Inventory Taking	Debit	G\L Account
81	Cost	Debit	G\L Account
82	inventory Difference	Debit	G\L Account
83	Price Difference	Debit	G\L Account
84	Consumption	Debit	G\L Account
85	Change in Stock	Debit	G\L Account
86	GR\IR Debit	Debit	G\L Account
89	Stock inwd movement	Debit	Material
91	Cost	Credit	G\L Account
92	inventory Difference	Credit	G\L Account
93	Price Difference	Credit	G\L Account
94	Consumption	Credit	G\L Account
95	Change in Stock	Credit	G\L Account
96	GR\IR Credit	Credit	G\L Account
99	Stock Outwd Movement	Credit	Material

Grid LIst, Subroutines, Reports

How to use a grid list?

Use Function Module Display_*LIST. In U’r program .Put all the data that U want to output in its final format and then pass this internal table to the function module

Two types of grid list .

DISPLAY_GRID_LIST(Version 4.0b)

DISPLAY_BASIC_LIST(Version 4.6b)

Calculate the subtotal etc and save it as a variant ,However while printing it will print all the enties of the fields

How to pass data from the form to the Subroutine program?

Use structure ITCSY

How can we pass selection and parameter data to a report ?

-     There are three options for passing selection and parameter data to the report.

. using SUBMIT...WITH

. using a report variant

. using a RANGE table

SAP EHS Online training

SAP: EHS

Environment, Health, and Safety

SAP Product Lifecycle Management (SAP PLM) addresses a range of environment, health, and safety issues. In addition to enabling you to manage risk and comply with government regulations, the solution integrates a variety of environment, health, and safety functions: 

• Product safety
• Hazardous materials management
• Dangerous goods management
• Industrial hygiene and safety management
• Occupational health
• Waste management

SAP PLM supports you throughout the life cycle of your products and assets across the entire supply chain, helping you continuously improve business processes. The solution's integrated architecture ensures the consistency of information exchanged between business and environmental, health, and safety processes. Current data is instantly available, and redundant data maintenance is avoided.

SAP PLM streamlines and automates all activities necessary to let you implement business processes safely, effectively, and in accordance with laws and regulations. The result is reduced costs and minimized risks, as well as an enhanced image and improved market opportunities.

SAP PLM – Environmental , Health And Safety

About the Training program

Sl.no	Session	Particulars	Duration
1	EHSO1	SAP Overview	2 Hrs
2	EHS02	EHS Overview	2 Hrs
3	EHS03	EHS Overview	2 Hrs
4	EHS04	ASAP Methodology	2 Hrs
5	EHS05	Introduction to ERP	2 Hrs
6	EHS06	Familiarization with SAP	2 Hrs
7	EHS07	Basic Data & Tools	2 Hrs
8	EHS08	Product Safety – I	2 Hrs
9	EHS09	Product Safety –II	2 Hrs
10	EHS10	Hazardous Substance Management - I	2 Hrs
11	EHS11	Hazardous Substance Management - II	2 Hrs
12	EHS12	Dangerous Goods Management - I	2 Hrs
13	EHS13	Dangerous Goods Management - II	2 Hrs
14	EHS14	Industrial Hygiene and Safety - I	2 Hrs
15	EHS15	Industrial Hygiene and Safety - II	2 Hrs
16	EHS16	Waste Management - I	2 Hrs
17	EHS17	Waste Management - II	2 Hr
18	EHS18	Occupational Health - I	2 Hr
19	EHS19	Occupational Health - II	2 Hrs
20	EHS20	Classification System	2 Hrs
21	EHS21	Reporting System - I	2 hrs
22	EHS22	Reporting System - II	2 Hrs
23	EHS23	Basic Workflow	2 Hrs
24	EHS24	Legacy System Data Migration	2 Hrs
25	EHS25	Roles And Profile Definition	2 Hrs
26	EHS26	Organization Structure	2 Hrs
27	EHS27	Integration With PP and QM	2 Hrs
28	EHSCE	CERTIFICATION EVALUATION	2 Hrs
		Total Working Hours	58Hrs