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.

SAP System Tables list

System Tables

ADCP	Person/Address assignment (central address administration)
ADIRACCESS	Table to store keys for TADIR objects
ADR2	Telephone numbers (central address admin.)
ADRP	Persons (central address administration)
APQD	DATA DEFINITION Queue
APQI	Queue info definition
D010SINF	ABAP- Information about ABAP program source code
E071	Change and Transport System- Object Entries of Requests/Tasks
E07T	Change and Transport System- Short Texts for Requests/Tasks
ENLFDIR	Additional Attributes for Function Modules
INDX	System table INDX
NAST	Message Status
STXH	STXD SAPscript text file header
T005	Countries
T005S	Taxes- Region (Province) Key
T005U	Taxes- Region Key- Texts
T006	Units of Measurement
T015M	Names of the months
T247	Month name and short text
T777A	Building Addresses
TADIR	Directory of Repository Objects
TBTCO	Job status overview table
TBTCP	Batch job step overview
TFDIR	Function Module
TFTIT	Function Module Short Text
TSP03L	Spool- Long device names
TSTC	SAP Transaction Codes
TSTCT	Transaction Code Texts
TUTYP	User Types in Current Price List in SAP System
TUZUS	Special versions
TVARV	Table of variables in selection criteria
TVDIR	View Directory
US930	Data Relevant to Measurement for User Master Record
USR01	User master record (runtime data)
USR02	Logon data
USR04	User master authorizations
USR06	Additional Data per User
USR14	Surchargeable Language Versions per User
USR21	Assign user name address key
ARCH_OBJ	Objects for archiving and reorganization
BTCUED	Description of user event IDs for background processing
BTXSUPB	BSI- Upgrade-Information
CCCFLOW	Client Copy Control Flow
DBSTATC	DB Optimizer Control (Statistics Creation)
DEVACCESS	Table for development users
DEVL	OBSOLETE- Do not use (See TCETRAL)
E070	Change and Transport System- Header of Requests/Tasks
E070L	CTS- Index for Assigning Numbers to Requests/Tasks
INSTVERS	Documentation for installation Status and History
PAT03	Patch Directory
SDBAC	DBA Action Table
T100	Messages
TAPLT	Program Application Long Texts
TASYS	OBSOLETE- Do not use, see TCEDELI
TDEVC	Development Classes
TEMSE	Temp Sequential table.
TLOCK	Change and Transport System- Lock Table
TNAPR	Processing programs for output. Can be very handy to find the print program for a SAPScript.
TNAST	Printed output control table
TPFET	Table of profile parameters
TPFHT	Profile header, administration data for profiles in DB
TPROT	Table contains all DD tables to be logged
TRBAT	Communication Table for Transport Control
TRDIRT	Title texts for programs in TRDIR
TRESN	Table of Naming Conventions in ABAP Workbench
TRJOB	Job ID for Coordinating Batch-ABAP/UNIX for Transports
TSP03C	Spool- Device Description Extension
TST03	TemSe data
TSYST	OBSOLETE- Do not use (see TCESYST)
TWSYS	OBSOLETE- Do not use (See TCETRAL)
USOBT	Relation transaction - authorization object
USR03	User address data
USR05	User Master Parameter ID
USR12	User master authorization values
USR40	Table for illegal passwords
USR41	User master- Additional data
UST04	User masters
VARIT	Variant texts
VARID	Variant directory
D010TAB	Table for Use Report---Tables
DD02L	SAP tables
DD02T	R/3 DD- SAP table texts
DD03L	Table Fields
DD03T	DD- Texts for fields (language dependent)
EDIDC	IDOC Control Records
EDIDOT	Short description of IDoc types
EDID2	IDOC segments (version 3.1)
EDID4	IDOC segments (version 4.6)
EDSEA	EDI- Table of all segments of current release
VRSX2	Central Table for Version Management (Report Source)
TSE05	Can add parameters to the INSERT COMMAND (IC). Then, when you insert command, your info appears in the editor. Useful for comment blocks, common section of code, etc.
CDPOS	Change document items
CDHDR	Change document header
T529A	governs the foreground sequence of infotypes the system will use to prompt the user during online and batch processing. You will have to code your BDC to follow that sequence of creating infotypes.
T588Z	governs the dynamic event processing that will only take place during online user inputs. For BDC's you will have to create separate BDC's to handle any infotypes that are inserted dynamically by this table.
T588M	Infotype Screen Control

What is ASAP Methodology

ASAP methodoligy means nothing but standard process for implementation of SAP,  It consists of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.
    Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the business and process requirements based on the
    Business Blueprint.
4. Final Preparation - The purpose of this phase is to complete testing, end-user training,
5.Go Live and Support

SAP BI routine Delivery Items

Delivery Items

CLEAR RESULT.

  RESULT = COMM_STRUCTURE-NO_DEL_IT.

  IF COMM_STRUCTURE-DOC_CATEG CA CREDIT.

    RESULT = RESULT * ( -1 ).

  ENDIF.

  RETURNCODE = 0.

SAP BI Routines Weight in Kilograms

Weight in Kilograms

CLEAR RESULT.

  DATA: WEIGHT LIKE COMM_STRUCTURE-NET_WGT_DL.

  IF COMM_STRUCTURE-UNIT_OF_WT NE 'KG'.

    WEIGHT = COMM_STRUCTURE-NET_WGT_DL.

    CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'

         EXPORTING

              INPUT                = COMM_STRUCTURE-NET_WGT_DL

              UNIT_IN              = COMM_STRUCTURE-UNIT_OF_WT

              UNIT_OUT             = 'KG'

         IMPORTING

              OUTPUT               = WEIGHT

         EXCEPTIONS

              CONVERSION_NOT_FOUND = 1

              DIVISION_BY_ZERO     = 2

              INPUT_INVALID        = 3

              OUTPUT_INVALID       = 4

              OVERFLOW             = 5

              TYPE_INVALID         = 6

              UNITS_MISSING        = 7

              UNIT_IN_NOT_FOUND    = 8

              UNIT_OUT_NOT_FOUND   = 9

              OTHERS               = 10.

    IF SY-SUBRC NE 0.

      clear MONITOR.

      MONITOR-msgno = '009'.

      MONITOR-msgid = 'SDBW'.

      MONITOR-msgty = c_msgty_e.

      MONITOR-msgv1 = COMM_STRUCTURE-UNIT_OF_WT.

      append MONITOR.

      RETURNCODE = 4.

      WEIGHT = 0.

    ELSE.

      RESULT = WEIGHT.

      RETURNCODE = 0.

    ENDIF.

  ELSE.

    RESULT = COMM_STRUCTURE-NET_WGT_DL.

    RETURNCODE = 0.

  ENDIF.

  IF COMM_STRUCTURE-DOC_CATEG CA CREDIT.

    RESULT = RESULT * ( -1 ).

  ENDIF.