CAREER ABAP

Day 1

2012-01-24T04:01:00.000-08:00

BO is a 30 years old French company. BO have the following kind of tools.

1. EIM (Enterprise Information Management) : In this space BO have 2 tools.

i) BODI (Business objects data Integrator)

ii) BODS (Business objects data services) : It is a combination of BODI, Quality Services.

2. EPM (Enterprise performance Management): In this space BO have a tool called as BPC (Business objects planning & Consolidation).

3. GRC (Governance & Risk & Control ): This tool is used to generate reports for scent lies calculations.

4. BI (Business Intelligence) : This space BO have the following BI tools.

i) Web I (Web intelligence)

ii) Crystal Reports

iii) Xcelsius

iv) BI widgets

v) Voyager

BI Stands for Business Intelligence. It is an approach to collect Business Data from different data sources, Integrating into big Data source ( Data warehouse) and generate reports to simplify decision making.

R/3 => BW => BEx

Data source Integration(Data warehouse) Reporting

Non-SAP => BODI => BO

Company Name	ETL Tool	DB Tool	Reporting Tool
SAP	BW/BODS	R/3, ECC	BEx/BOBI
Oracle	ODI(Oracle Data Integrator) ODW	SQL, PL/SQL	SIBEL Analytics
IBM	Data Stage	DB2	Cognos
Microsoft	SSIS	SQL Server	SSRS/SSAS

Available ETL Tools in the Market

1. Informatica => Informatioca Corporation

2. BW/BODS => SAP

3. Data Stage => IBM

4. JCM => Apple

5. Abentio => Abentio Corporation

6. ODW => Oracle

7. SSIS => Microsoft

Available DB tools

1. SQL/PLSQL => Oracle

2. My SQL => Apache

3. SQL Server => Microsoft

4. Sy Base => Sy Base IQ

5. Tera Data => NCR Corporation

6. NETEZZA => NETEZZA Corporation

7. DB2 => IBM

Available Reporting tools

1. JASPER => Apache

2. BOBI => SAP BO

3. Cognos => IBM

4. Micro Strategy => Micro Strategy Corporation

5. JERKING => JETKING

6. SSRS => Microsoft

7. Sieble Analytics => Oracle

Hardware & Software Requirements

1. Non-SAP BO Installation:

HDD : Minimum 5 GB Space

RAM : 512 MB

Processor : Any Processor (Celron, Pentium, ……)

OS : ALL O.S ( XP, W7,Vista, Unix,…………..)

2. SAP BI BO (Without ECC)

HDD : 20 GB

RAM : 2GB/3GB

Processor : Dualcore and Above

OS : All O.S

=> Explain me what software the developer required in their load system to create SAP BIBO Reports and what software the End-user required to access ?

In the Developer machine they need the below software

a. SAP GUI

b. Business Object (BO) Client

c. Integration Kit Between SAP BI & BO

MDX SQL

d. Crystal Reports (online) (OLTP)

e. Xcelsius (For Dash Boards)

f. Voyager

g. Widgets (For mobile Reporting)

End user need not to install any S/W, in their load system, They can access all the reports through the web by using the Infoview portal.

è Comparison between SAP & Business Objects

Report Type	SAP Tool (.BEx)	BO – Tool
Ad Hoc (Drill – Down)	BEx Analyzer	WEBi
OLTP(Transactional Reports/online)	Report Designer	Crystal Reports
Dash Boards	WAD (Web Application Designer)	Xcelsius
Portal	EP (Enterprise Portal)	Info view
ETL Tool	BW	BODS (New Version) BODI – Older Version

Delete PM Notifications

2011-12-16T02:16:00.000-08:00

To delete the PM Notifications, first we need to set the PM notifications to status "Complete". We can achieve the same by following steps:

Go to Transaction "IW28".
Provide the necessary information on the initial screen
A list of PM notifications based on the data provided earlier is displayed.
Select the list of PM notifications which needs to be deleted and hit the button "Complete" (Flag with Black & White check mark) or CTRL+F9.

After setting the status as complete, now we would set the deletion flag for the same. This can be achieved using the transaction "IW27".

To delete the notifications, use the archiving transaction "SARA" and the object to be used is "PM_QMEL".

Best Computer Training in SAP ABAP in Hyderabad

2011-11-06T21:38:00.000-08:00

Invent - IT in Ameerpet, Hyderabad

4/5 based on 7 reviews Rating Details Rate This Business

teaching faculty : Raju Having 7 years of teaching exp...

Category:
Computer Training

Address:
#31, 2nd Floor
Gayatri Nagar
Ameerpet, Hyderabad -500016
Landmark: Behind Huda Center
Mobile:
8142813133
Email-id: sap.invent.it@gmail.com

Contact Invent - IT In Ameerpet Or Save For Later Reference

Business Details for Invent - IT in Ameerpet, Hyderabad

Business Days:Monday - Saturday
Business Hours:7:00 am - 9:00 pm

Additional Information for Invent - IT in Ameerpet, Hyderabad

Invent IT is here in this field from past several years. We are one of the best coaching providers in Hyderabad. We are dealing with SAP/other ERP and .Net. Contact us for further details.

Customer Relationship Management (CRM),

2011-08-30T01:41:00.000-07:00

Difference between EEWB and BDT

Configurations for opening an external URL (like SAP.COM) from IC WebClient.

Adding Web URL (like google.com, yahoo.com) in CRM UI

Creation and Configuration of Business Partners

Action Profiles in SAP-CRM

Difference between EEWB and BDT

2011-08-30T01:33:00.001-07:00

Difference between EEWB and BDT

BDT, among other things, is used to add/delete/disable fields in the BP transaction only. It does not create new objects for the developer to play with. BDT as a separate unit in CRM (TCode BUPT) has several useful tools like BP events which are useful at times.

Whereas EEW can extend several transactions in CRM including BP and it extends the business object by creating several z-objects like an active BADi implementation, middleware objects like z-function modules which you can use for coding your custom logic.

But there's a lot in common for BDT and EEW - they both create the field groups, views, sections and screens when you enhance an object. You can use BDT to change titles such as tab name or section name after you have created the easy enhancement project for a particular object!

Configurations for opening an external URL (like SAP.COM) from IC WebClient.

2011-08-30T01:32:00.000-07:00

Configurations to open an external url (like SAP.com) from IC WebClient

Web URL inside CRM IC Web BSP view can be launched using transaction launcher. Follow the steps below:

First create URL ID using the path IMG->CRM->IC WebClient->Basic Functions->Transaction Launcher->Define URL's and Parameters
Here by clicking on New Entries ,you need to create a URL ID, select 3rd radio button Non BSP URL and enter your web URL there. To keep it simple copy the existing URL ID SAP into your own with your web URL for ex ZSDN
Now go back to Transaction Launcher and start the "Configure Transaction Launcher" Wizard
In the Wizard when it prompts for Launch Transaction ID ,enter new transaction ID for ex ZTXID_SDN and click on 'continue ' and enter transaction class name for ZCL_TX_SDN
In the next screen under 'Transaction launcher Type' select 'URL Transaction' ,and under details area select the URL ID you have created in step 1. i.e ZSDN.
Complete the wizard.
Now you need to map the URL transaction ID to Navigation Bar profile entries.
For this go to 'Define Navigation Bar Profiles' under Basic Functions.
Click on Define Entries ,enter the basic details and select 'Launch Trans' radio button and select the transaction id created in step 2 . i.e ZTXID_SDN
Add the above create entry to your Navigation Bar profile
Update IC Web Client profile with your Navigation bar profile
Launch IC web and you would see Web URL Navigation bar entry under Navigation Bar.

Adding Web URL (like google.com, yahoo.com) in CRM UI

2011-08-30T01:30:00.000-07:00

Web URL (E.g. Google, Yahoo, etc) in CRM UI can be launched using transaction launcher

Step1:

Step1a: Call Transaction SM30. Enter the View name: CRMV_IC_LTX_URL

Step1b:

URL ID: ZGOOGLE (any name starting with Z)

Description: Google

Request Method: Get

Click radio-button for Non-BSP URL

URL: http://www.google.com

Save the entry.

Step2:

Step2a:

Call transaction CRMC_UI_ACTIONWZ

IMG path CRM -> UI Framework -> Technical Role Definition -> Configure Transaction Launcher

Step2b:

Launch Trans. ID : Zlaunch_google.(Any name starting with Z)

Component Set : ALL

Click on Continue.

Step2c:

· Description : launch google

· Class name : ZCL_CRM_LAUNCH_GOOGLE (Any class name starting with Z).

· Activate checkbox for ‘Stateful’ to show the URL in a new window.

· Be sure that the checkbox ‘Raise Veto’ is deactivated.

· Click on Continue

Step2d:

Choose URL Transaction (B) as transaction type

URL ID: ZGOOGLE created in the URL repository.

Continue

Step2e:

Skip screen for transaction parameters and activity clipboard by pressing ‘Continue’.

End the wizard and press ‘Complete’.

Step3:

Step3a:

Execute Transaction CRMC_UI_NBLINKS

IMG path CRM -> UI Framework -> Technical Role Definition -> Define Navigation Bar Profile

Select ‘Define Logical Links’ at the dialog structure on the left by double-click.

Create a new logical link:

Logical Link ID: ZGOOGLE

Type: Launch Transaction

Target ID: EXECLTX

Parameter ZGOOGLE

Parameter Class: CL_CRM_UI_LTX_NAVBAR_PARAM

Title: Google

Description: Google

Save the changes.

Step3b:

Select ‘Define Direct Link Groups’

Create a new entry

Group ID : ZGOOGLE

Group Type : No Classification

Title : Google

Description : Google.

Step3c:

Select ‘Assign Links’ at the dialog structure on the left by double-click.

Create a new entry

Logical link ID : ZGOOGLE (Which has been defined in Define Logical Links)

Position : 10

Save the changes.

Add the link which was created in Define Logical Links.

Step3d:

· Select ‘Define Profile’

· Select profile corresponding to web UI

· Click ‘Assign Direct Link Groups’ at the dialog structure on the left

· Create a new entry

· Group ID : ZGOOGLE

· Position : 30 (any position).

Step4:

· Execute Transaction CRMC_UI_PROFILE or go to IMG path CRM -> Business Roles -> Define Business Role.

· Select business role ZWOOSALESPRO (the role which is assigned to user)

· Double-click on ‘Visible Direct Group Links’ at the dialog structure on the left.

· Click Visible Check Box corresponding to Group ID ZGOOGLE

Step5: In the Web UI the link appears as shown below.

Creation and Configuration of Business Partners

2011-08-30T00:33:00.000-07:00

Introduction

This document is the Business Process Design of the Business Partner Master data for SAP CRM. It describes the interpretation of the SAP CRM object Business Partner (abbreviated BP).

Objectives

The aim of this document is to acquire all information needed for the customizing object BP in SAP CRM.

Business Partner

Defining Number Range

In this activity, you define number ranges for business partners.

The defined number ranges are assigned to groupings in the Define groupings and assign number ranges activity. Number ranges for business partners are valid throughout a client.

Procedure

1. Access the activity using one of the following navigation options:

SAP CRM Role Menu	Defining Number Range for Org Business Partners
Transaction code	SPRO
IMG Path	Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Number Ranges

2. Choose Change Intervals

3. Choose Insert Interval.

4. Enter the Interval ID and range

5. Select Check Box Ext if External Number range is required

6. Save your Entries

Result:

The Number ranges are defined as needed for different kinds of roles of Business Partner.

Defining Groupings

Use

Assign each business partner to a grouping when you create the business partner. This grouping determines the number range.

You cannot change this assignment at a later stage.

Procedure

1. To carry out the activity, choose one of the following navigation options:

SAP CRM	Defining Groupings
Transaction code	SPRO
IMG path	CRM à Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Groupings and Assign Number Ranges

2. Choose New Entries.

3. Enter the grouping, short name, description, number range and select the check box External.

4. Save your entries.

Result:

All the Number Ranges defined are assigned to a group with a particular naming convention, which are used in Grouping Tab in Easy Access Screen of Business Partner.

Defining Business Partner Roles

Definition: Business Partner role

Rights and responsibilities that a business partner can have in various business transactions.

In this activity, you make the settings for the properties of business partner roles.

In the business partner dialog you can select from all of the business partner roles provided. If you only want to display certain business partner roles in the selection list, you can hide the other business partner roles.

You can replace the standard title of business partner roles with customer-defined names

Procedure

1. To carry out the activity, choose one of the following navigation options

SAP CRM	Defining Groupings
Transaction code	SPRO
IMG path	CRM à Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings àBusiness Partner Roles à Properties of Business Partner Roles

2. Select New Entries.

3. Select the required Business Partner Role.

Set the indicator Hide if the business partner role is not to appear in the selection list.
Define the position where the business partner role is to appear in the selection list.
If you want to give the selected business partner role a different title to the standard title, enter the required Customer title under Title.
Save your Entries

The following roles will be used in SAP CRM:

Role Name Category (Person/Org/Group) Remarks

Employee	Person	Use of Standard role Employee
Contact person	Person	Use of SAP standard role contact person
Sold to Parry	Person/Organization	Use of SAP standard role sold-to party
Prospect	Person/Organization	Use of SAP standard role prospect
Ship to Party	Person/Organization	Use of SAP standard role Ship to Party
Bill to Party	Person/Organization	Use of SAP standard role Bill to Party
Retailer	Person/Organization	This role will be used to register the retailers.

Result.

All the Business Partner roles those the client wants to appear in the Easy access Screen are defined and all those that are unwanted are hidden.

The Business Partner Roles are named in accordance with the client’s requirement.

Creating a Business Partners

Procedure

1. Access the activity using one of the following navigation options:

SAP CRM Role Menu	Checking Business Partners
Transaction code	BP
SAP Menu	Master Data à Business Partner à Maintain Business Partner

2. Go To create Person

In the field display Role Choose sold to party and in Grouping Choose Customers Grouping

3. Enter all the required data, like Title, Name, Address and also the data as required the other tabs

4. Save the entriy.

5. Repeat the same for different roles.

Result.

Business Partners are created with required roles.

Action Profiles in SAP-CRM

2011-08-30T00:30:00.000-07:00

1 INTRODUCTION

1.1 ACTIONS

Actions are used in maintaining and improving business relationships. We can schedule and start predefined conditions with the Actions component by means of user-definable conditions from transaction and marketing objects.

Actions use the Post Processing Framework (PPF), a Basis component, which can be automated with the initiation of outputs, follow-on documents or workflows. Using the Actions tab page within a business document, you can display a list of actions that can be included in the business transaction.

An action profile is determined from the corresponding transaction type or item category.
Actions are stored as action definitions within an action profile.
You can control action processing using different settings and parameters:
Action changeable or executable in dialog
Action displayed in toolbar (SAP GUI)
Processing time (when saving the document or via selection report)
Partner dependence
Determination technique
Action merging
Processing types (with entry of the desired form name)

1.2 FEATURES OF ACTIONS

You can define actions dependent on conditions so that the system automatically schedules and starts them when the conditions are fulfilled. With actions you can:

Create follow-up transactions automatically
Execute changes in the transaction or marketing object currently being processed, for example, create new items, or status inheritance by subordinate elements in marketing objects
Output in print, by faxing or e-mail

Actions are displayed in transaction documents that support actions and to which an action profile is assigned. You can display a list of actions scheduled for the document on the Actions tab page of a transaction document. The following information is displayed in the list for each action:

Status (action scheduled, action processed)
Description (purpose of action)
Conditions (settings for action definition and conditions are displayed)
Creator, Creation date

There are various processing types for actions:

· Methods (Business Add-Ins)

Methods are Business Add-In (BADI) implementations. You can define your own BADI implementation to adapt actions to your processes and needs. (EXEC_METHODCALL_PPF is the relevant BADI.)

Examples for standard methods include the following:

COPY_DOCUMENT (create a follow-up document)
COMPLETE_DOCUMENT (set status completed within document)
CREDIT_MEMO (create credit memo item)
REPAIR_ITEM (create a repair item)
1O_EVENT_CREATE (create a workflow event)

· SAP Business Workflow

This is suitable for more complex processes, for example, a follow-up transaction that includes an approval process.

· Smart Forms

SAP Smart Forms must be used to print, e-mail or fax documents such as an order confirmation. You can use the graphics tool, SAP Smart Forms, to design the layout of output forms.

SAP delivers several Smart Forms for outputs in SAP CRM:

Form CRM_ORDER_CONFIRMATION_01 (suitable for faxes, letters, and e-mail)
Form CRM_ORDER_LEASING_01 (suitable for faxes, letters, and e-mail)
Form CRM_OPPORTUNITY_01 (suitable for faxes, letters, and e-mail)

SAP Smart Forms offer the advantage of adapting forms without requiring programming knowledge, thanks to a completely graphical user interface.

When you request a printout of a form, the application program obtains the relevant data to be used and prints it on the form. Data retrieval and form logic are separated from one another.

SAP Smart Forms replace SAP-Script forms (migration from SAP-Script forms to Smart Forms is supported).

2.0 HOW TO CREATE AN ACTION

2.1 STEP-BY-STEP PROCEDURE

2.1.1 Enter into any SAP-CRM Server and move to Transaction SPRO.

2.1.2 Press SAP Reference IMG -> Customer Relationship Management ->Basic Functions -> Actions -> Actions in Transactions.

2.1.3 To create an Action Profile – Click on . First read the documentation.

2.1.4 Now Press the Execute Button to start creating an Action Profile.

2.1.5 Click . Enter the Details to create Action Profile.

2.1.6 Click . Enter the Details to create Action.

2.1.7 Click . Enter the Details to set Action.

In the Processing Time Details, there are 3 Options.

Processing Using Selection Report gets started after a selection report is executed if the start condition has been fulfilled.

Immediate Processing gets started as soon as the start condition is fulfilled.

Processing when saving a Document gets started when the document is saved.
2.1.8 Click . Enter the Details to Set Up Partner Determination.

Partner Dependent makes this Action as dependent on Partner. The partner you choose is the one, for which the action triggers. It first checks whether that Partner exists or not. If not, it throws an ERROR.

2.1.9 Click and select the Processing. The processing that we select is the one on which we want the Action to work on.

Processing can be of various types such as:-

Select the one you want. For this case select Workflow.

2.1.10 Click and Enter the Workflow Number that you want to assign with this Action.

2.1.11 Click and Enter Action Description.

2.1.12 Click and assign Schedule Condition.

Schedule Condition decides whether an action should be scheduled for processing or not. An action is therefore generated only if the schedule condition is met. It is not mandatory to assign a schedule condition.

Select anyone that suits your requirement and proceed further.

2.1.13 Click and assign Start Condition.

Start Condition is checked before an action is executed. The Action is executed only if the Start Condition is satisfied.

Here you won’t be able to assign a Start Condition; there is another tab in Actions where we can assign Start Condition.

2.1.14 Click and Action Configuration is complete.

Click and save it in a Transport Request.

2.1.15 To assign Start Condition -> Go-to step 2.1.2 -> Click on Change Actions and Conditions -> Define Conditions.

In Scheduling of Actions, find your Action – Test an Action Profile.

It shows you the entire Action that you created till now.

To assign start condition, Click on Start Condition Tab.

Click Edit Condition to enter a condition.

Enter a Condition.

Click ‘√’.

Click on SAVE. Save it in the same Transport Request as Earlier.

And hence, this completes your Action Profile Creation for a Workflow.

Similarly, we can create Action Profiles for other processing also.

Production Planning (PP)

2011-08-29T03:23:00.001-07:00

Types of Subcontracting
Difference between Co-Product and Bi-Product with an example

Converting Planned Orders to Purchase Requisitions and Purchase Orders

Routing Vs Task list Vs Work Procedure

Production Order Splitting

Repetitive Manufacturing Cycle

Typical Production cycle in Process Industry

MRP Run in background for all Network Plants

Types of Subcontracting

2011-08-29T03:09:00.002-07:00

There are two types of subcontracting relevant for PP module:

Operation subcontracting
Assembly subcontracting.

Operation subcontracting: Within in-house production if some capacity bottlenecks exists in any operations then you can this job to some vendors to carryout this job at his premises and supply us the semi-finished part. This can be done via control key example PP02 (external processing).

Assembly subcontracting: Total product can be given for subcontracting. We have to give the raw materials to vendors and they would supply the assembly. This can be done with special procurement type 30 with procurement type F.

Difference between Co-Product and Bi-Product with an example

2011-08-29T03:09:00.001-07:00

If you look at a petro chemical refining industry their main input material will be "Crude oil" during refining they get "Petrol", "Diesel", "Kerosene", "Naptha" & "Water" etc...

So the whole of the production cost should not go to "Petrol" alone, as Diesel, Kerosene and "Naptha" are also sellable. Water is not sold out, but is being used internal for the operation.

In this scenario "Petrol". "Diesel", "Kerosene" and "Naptha" are defined as co-products in the material master. And the cost which needs to be distributed among them are in the ratio 30:30:20:20, so in the joint production details we select the apportionment structure, and here we define the equivalence number by entering the materials and numbers as required by us as 30:30:20:20.

Now BOM is defined for the main product "Petrol" and Diesel", "Kerosene", "Naptha" and Water are defined in -ve quantity. Here the definition of water goes as "BiProduct". Crude oil is defined as component in +ve quantity. Now during order costing/product costing/settlement considers the entire cost of production based on the crude oil cost and infrastructure cost and it splits into the ratio defined in the equivalence number.

Converting Planned Orders to Purchase Requisitions and Purchase Orders

2011-08-29T03:08:00.003-07:00

We can create planned orders & convert them into purchase requisition or into production order.

In the material master ,MRP2 view give the procurement type as 'X', for both internal & external procurement.

Also include purchasing view for this material.

When you run MRP using md02, a planned order will be created for the requirement (Eg: say 100 no's given using transaction code MD61).

Use transaction code MD04 to view the stock/requirement list.

Here double click the planned order, you can see tabs such as convert into purchase requisition, into production order, into process order.

Click convert into Purchase Requisition & enter 50 Nos. Then a Purchase Requisition will be created which can be further converted into Purchase Order.

Again come to md04 screen.

You can see a planned order & Purchase Requisition for 50 no's.
This planned order can be converted into production order & 50 no's can be produced internally.

Routing Vs Task list Vs Work Procedure

2011-08-29T03:08:00.001-07:00

Task list means the task which has to carry out on the shop floor and these are six types as you have mention.

Routing is one of task list and this consists the series of operations requires for the production of an assembly at shop floor.

Regarding the work procedure, you can define this in the work center default tab for the details about the work center and how to operate. this will be copied in operations while creating routings.

Production Order Splitting

2011-08-29T03:07:00.001-07:00

Production Order could be split due to following reasons:

When partial lot of order is to be handled from the rest due to quality reasons.
If capacity bottle necks exists.
Material is committed for part of order qty.

Features:

The split operations and the material assigned are copied into the child order.
The structure of the parent order does not changes while the split off operations are copied into the child order

Status for parent order : SPLT
Status for the child order: SPLE
For operation : SPLT

Restrictions:

The parent order and the child order must be settled to same cost collector
Read PP Master data is not possible
Confirmations at header level is not possible

Steps to perform split:

In OPL8 Set the indicator cost collector
Default Rule -Periodic settlement(PP2)
CK11N do standard cost estimate
KKF6N Create cost collector
Create production order with op10,20,30,40
Go to op overview
Select the op from which you want to split (exop20)
Go to functions ----> Split order
Enter the qty ,if necessary a different order type for the child order
Execute
Order will be splitted .
The order can be splitted even from op10 itself
Goto MD04
Two orders will be created
Go to op overview of each order and there you can see the splitting.

Repetitive Manufacturing Cycle

2011-08-29T03:06:00.000-07:00

Create REM Profile using SPRO

SPROàProductionàRep ManufacturingàControl Dataà Create REM Profile Using Wizard.

Save the profile and exit from SPRO.

1. Create Material Master with Fert and ROH as usual.

2. Create BOM as Usual.

3. Create Production Line with Capacity Category as : 0007 (i.e normal work center)

4. Create Rate Routing for Fert Material using TC: CA21

5. Go to Change Material Master (Fert Material ) and Attach REM Profile, Mark tick indicator for REM Manufacturing. In MRP-4 View.

6. Create Production Version for this Fert material.

Select BOM, Select Rate Routing with No.

Defn: REM Profile

Repetitive manufacturing profile

Controls, via order type, whether you are working with make-to-order repetitive manufacturing, based on sales orders, or with make-to-stock repetitive manufacturing, based on no specific orders.

Use

The repetitive manufacturing profile also determines;

How the system deals with activities when back flushing
Which movement type is used to post goods receipts and goods issues
How planned order and run schedule quantities are reduced in the
Back flush transaction
How BOM corrections are made - if errors should occur when posting
Quantities to be back flushed

Dependencies

Repetitive manufacturing profiles are defined in Customizing for Repetitive Manufacturing.

Material Screen Shot:

Click on Production Version:

Enter the Prodn Ver No., Validity Period.

Double Click Selected line.

Enter The Necessary Data as in Item no.6.

Click on Check button to check the entries:

Green light should glow (if there is any inconsistency found then it glows with red color).

Save The Material Master and Exit.

Step No: 3

Create Independent Requirements TC: MD61

Step No:4

Run MRP TC: MD02

Step No: 5

Go to Planning Table TC: MF50 and assign the quantities to production line.

Run Schedule Quantities are assigned and go to MD04 all planned order are converted to RS Qty.

Step No 6:

Create Product Cost Collector for Fert Material: TC: KKF6N

Click on Create icon

Note: Maintain Division in Accounting View 1 for Fert Material which as linkage between business area and division, Valuation area.

Step 7:

Do the Back flush Using TC: MFBF

Enter and save the file….

This is end of Repetitive Manufacturing Cycle.

Typical Production cycle in Process Industry

2011-08-29T03:04:00.000-07:00

The below production cycle explains the basic business flow in “Process Industry”. The flow is generally focusing only on Production and Quality Management

Simple Production Cycle:

Consider all Raw materials are available in plant and production process yet to start, the following stages are to be followed

1. Create Process Order

Here we are creating a process order based on the capacity of the equipments and resource availability

2. Release the Process order

Once Process order created, it has to be released for production, means system will check the scheduling, material availability, capacity planning, etc., and then release process takes place

3. Goods issue from the Stores

Once PO got released, goods issue against the process order will takes place

4. Start processing

Product process against the PO will start

5. Confirmation Process

After production, the final out put confirmation from the process will be entered

6. Goods Receipt Process

Goods receipt process plays a major role in any business here we have to do 101 movement type and do the postings. In goods issue process they will issue the goods against PO in 261 movement type.

7. Quality Approval and Release

Once GR from the production was made, the material will come to Quality control for approval. Here QC person will check the material and they will do the result recording and usage decision

8. Stock will appear in Unrestricted use for SALE / Further Process

Once usage decision was made the material will automatically moved into unrestricted use. The FG is ready for sale

By keeping above all points in mind, the following masters and transactions are required to proceed

S. No	Master	Trans-action	T-code	Description	Where has to be used
1	√		MM01	Create Material	Used for creating Recipe and further tracking
2	√		CRC1	Create Resource	Machine / set of Machines used for making the product
3	√		C201	Create Recipe	Here we are calling resource and materials required to make the finished product
4	√		QS21	Create MIC	List of specifications to be checked for that concerned finished goods
5	√		QP01	Create Quality Plan	Creating Quality Plan
6		√	COR1	Create Process Order	Initiating Production Process by creating Process Order
7		√	MIGO with 261 movement	Goods Issue Process	Goods issue to Manufacturing unit
8		√	CORK	Confirmation Process	Production Output confirmation Process
9		√	QA32	Quality Approval and Usage Decision	QC will approve and release for further process

Step by Step Execution Process:

Scenario Explanation:

REQUIREMENTS:

For a leading Process Manufacturing Company ABC, they are selling the product “FG 1”, the raw materials and resource requirements are listed below

Raw Materials required for making 50kg of Finished Product, FG 1 are

S.No	Material Code / Material Type	Material Description	Quantity required	Unit of Measurement
1	RM l 1 / ROH	Raw Material 1	80	Kg
2	RM 2 /ROH	Raw Material 2	20	Kg
3	BP 1 / FERT	Byproduct	60	L

Resources required for making 50kg of Finished Product FG1

S.No	Resource Code	Resource Description	Capacity
1	CRC-001	Reactor	2KL
2	CRC-002	Vessel	4KL

List of MASTERS required for addressing the above scenario

1. Create Materials using MM01 transactions in the following way:

In this screen select “select views” button and extend the following fields

We have selected basic information entries field. Fill the information and finally select the General plant / storage data and give plant as 1100 and storage as 0001 in case of Raw material.

The same procedure has to be repeated for finished goods and Co-Products, in plant storage data we have to give Plant 1100 and storage 0004.

2. Create Resource master using CRC 1 Transactio

Here we have to mention the Person responsible and standard value type “SAP1 – Normal Production”.

Here we are planning to give the controlling area and cost center. Finally save the data. The same procedure has to be repeated for CRC-002

3. Create Recipe using resource and material in T-code C201

In the above screen we have to enter the material we want to produce “FG 1”, and give the plant code and profile “PI01” then enter.

In the recipe header we have to enter the status as “4” and Usage as “1” , go for Operations screen

Here we have to call the resource and the description details, for example in reactor CRC-001, the operations like Heating and transfer process will be carried out the same has been explained in this description field. As per standard value key we have to give the duration for the operation time and labor time. Both will be taken for scheduling.

In the material tab, we have to enter the version for the BOM and usage details, after that we have to enter the list of raw materials required for making 50 kg of the FG 1 product. Here co-product is generating so we have to give the co-product “BP 1” 60 L as “Negative” producing after the process (NOT as INPUT) and activate as Co-Product by selecting the line item and press items tab and select co-product tab.

In the header level line item we have the base quantity i.e Finished goods quantity, give 50 and save

Now Recipe is ready.

4. Create MIC using QS21 transaction

Here give the short text, field search and int. char.desc as pH and select the Quantitative check box.

pH have some ranges so, we have to select the limits are upper and lower spec limits.

The same way we have to create temperature also

5. Now create the Quality plan using QP01

Now we are planning to create the quality plans which are to be tested before release from QC

Header data details as above

Then Go to operations and give control key as QM01, select the line item and go to inspection description tab.

Enter the MIC details here. While entering system will ask the upper spec and lower spec limits. Enter limits and save

Masters are ready to proceed the Production Cycle

We will start Production Cycle using transactions

1. Create Process Order using COR1

Here give the total quantity as “50” and enter the start date, system will check the scheduling and capacity planning and finally finish date will come.

Now, once the process is over check the master data, in that we can find the created recipe group for that material “FG 1”

Now the PO stated us “Created”

Press the Flag button and ‘Release” the PO for production. After pressing flag button, actually system will checks material availability, scheduling, capacity planning etc., Once it is over the status of the PO will be changed to “Released mode”

Save the Process order.

2. Goods issue against the Process order using MIGO Transaction

Goods issue generally happens from store against the PO with the movement type 261

Once goods issue from the stores is over, the document number will be generated as below

Now go to process order and check the order status “GMPS” will appear, that means Goods Movement Posted

Now Production process was started and completed. We are going to give confirmation using CORK transaction

3. Confirmation using CORK Transaction

Once you enter, the yield quantity you have to confirm

Here in MM01, Quality Management views we have to activate the inspection lot origin “04” for inspection triggering while making Goods receipt using 101 transaction. The following procedure has to be adopted.

Select Inspection set up tab and activate 04 inspection type.

This activity has to be done at the time of creation of Master (MM01)

4. Goods Receipt using MIGO with movement type 101

If you check this screen the outputs finished product 1 and co product 1 with the quantities viz., 50 and 60 will be there. We have activated QM view only for FG 1 and not for BP 1 material. So once GRN was made the material FG 1 will be automatically moved to Quality inspection and BP 1 will be moved to “unrestricted use”.

At the time of GRN we are creating the batch for FG 1 as “FG00000001”

For BP 1 we are creating Batch as “CO00000001”. The batch can be created at the time of creation of Process order also.

Here we are mentioning the storage location for the final products “0004”

Once GRN made the document number will be generated for Accounting updates

5. Quality Approval and Release

Now check the MMBE view, in that the material FG 1 appears in “Quality inspection”

And at the same time BP 1 in which QM was not activated, the stock appears in Unrestricted use

Result recording and Usage decision process for the Material FG 1 batch FG00000001

Go to QA32 and give the inspection lot origin as”04” and press enter

Check the status. The system status should be “RELEASED”

Press “Results” button and do result recording

After entering the actual value the final screen will be like below

Now, go to Usage decision button in the same QA32 Transaction and do accept the batch

Once you save the inspection stock details will come

Enter the stock quantity “50” to unrestricted and check the MMBE view now

Material will be moved to unrestricted use . Now sales process will start.

The above cycle is simple production process generally carried out in “Process industries”

MRP Run in background for all Network Plants

2011-08-29T03:02:00.000-07:00

Purpose:

To understand how to take MRP Run in Background for All Network Plants, using Transaction Code:-MDBT.

Scope: To view Background MRP List.

Method:

Please follow the procedure as given below:

Transaction code	MDBT
Menu Path	SAP menu à Logistics à Production à MRP à Planning à Total Planning à MDBT--Background MRP

After filling information please click on Attributes. Here you need to do configuration for Scope of Planning (TCode: OM0E) or you can select single plant also. In Scope of planning you take multiple plants.

Here you select different option as per your requirement like protect variant.

After Saving Variant you will get Variant SCM VB Saved.

We need to start our background MRP Run through Tcode- MDBT.

Then go Tcode: SM37- Job Overview

After Successful completion of Background Job, please select the Job & then Click on Spool

Here you will MRP list generated through Background MRP Job. This list will show which materials are
planned with Plant & their exception group.

SAP Financials (FI)

2011-08-26T05:21:00.000-07:00

Check duplicate creation of Vendor Master that have the same address data through standard SAP settings

Validation rules in FI

Defining Asset Number Range

Steps to configure Document text in Customer Invoice Entry (FB70) transaction

Understanding Lockbox

Information on FICA (Finance and Contract Accouting)

Comparison of FI and FICA

Check duplicate creation of Vendor Master that have the same address data through standard SAP settings

2011-08-26T05:14:00.001-07:00

Requirement:

Check duplicate creation of Vendor Master that have the same address data through standard SAP settings.

Solution:

An information message will be shown to user when he is creating Vendor master data which will inform him that Vendors already exist with the same data in address fields. Then the Vendors with the same address will be displayed to the user. From here if he selects continue button he will be allowed to create the Vendor, if he selects the cancel button he will be given the option of making changes to the address fields.

Configuration Steps:

Goto SPRO: SAP Reference IMG:

1. Financial Accounting(New)->Accounts Receivable and Accounts Payable->Vendor Accounts->Master Data->Preparations for Creating Vendor Master Data->Change Message Control for Vendor Master Data

2. The following screen will be displayed where you can define your message for Ex:

F2 144 – Vendors found with same address; check

Set the values Online = ‘I’ and BatchI (Batch Input) = ‘I’

If you want to make this check user specific then enter the User Name else leave it blank to make it applicable for all users.

Again go to SPRO:

Financial Accounting (New)->Accounts Receivable and Accounts Payable->Vendor Accounts->Master Data->Match Code->Check Search Fields for (Vendor) Matchcodes

The standard fields on which the check is performed are:

NAME1
NAME2
ORT01

So when user creates a Vendor with NAME1, NAME2 & ORT01(City) fields same as an existing Vendor the system will show an Information Message. The value in these fields is automatically converted into Upper case so you do not have to worry about case- sensitivity.

When the user clicks the continue button on the message popup the Vendors having the same address data will be shown to the user & he can navigate to view the details of these vendors.

Validation rules in FI

2011-08-26T05:13:00.001-07:00

In the SAP R/3 System, nearly all input values are validated by a program or against tables or master files. Since some types of validations cannot be standardized, you can use the validations program to create validations for your specific requirements.

The validation function enables you to check values and ranges of values as they are being entered in the SAP R/3 System. Validation rules are stored in the Rule Manager. As data is entered into the system, the Integration Manager validates the data against the validation rules. Because data is validated before it is actually posted, only valid information is posted to the FI-SL application component.

The system validates account numbers against a master file or checks that a ledger is assigned to a local company code.

You use validations when you want to create a user-defined Boolean statement to validate an entry in a way that is not defined for the standard system.

A validation can consist of up to 999 steps. You can therefore validate data against any number of Boolean statements before the data is posted.

Creating a Validation:

1. Go to transaction GGB0 and select the application area-Financial accounting from the tree menu. Select the node: Line item.

Click on the “Validation” button available on the application toolbar to create the validation and enter the following details:

Validation name: VB15_V2

Description: Validation for the tax code

Message ID: ZFGL

Call up Point: 2

Application area: FI

Click on ‘Save’.

Note: Validations can be created for all the application areas of FI available on the screen of GGB0 as shown above.

2. Now click on “Step” button on the application toolbar to create the validation step with the below details:

In the “prerequisites” sub node enter the below condition: (This validation rule should trigger only for transaction FB01,FB60,FB65,FB02,MIRO,FV60,FV65,FVB0,FBM2,FBV0,FBV2,F-01,F-44,and only for vendor line items(KOART= ‘K’)

(BKPF-TCODE = 'FB01' OR BKPF-TCODE = 'FB60' OR

BKPF-TCODE = 'FB65' OR BKPF-TCODE = ‘MIRO’ OR

BKPF-TCODE = 'FB02' OR BKPF-TCODE = 'FBM2' OR

BKPF-TCODE = 'FBV0' OR BKPF-TCODE = 'FBV2' OR

BKPF-TCODE = 'FV60' OR BKPF-TCODE = 'FV65' OR

BKPF-TCODE = 'F-01' OR BKPF-TCODE = 'F-44’) AND

(BSEG-KOART = ‘K’)

3. In the “message” sub node, enter the details of the error message that needs to be displayed.

4. Go to transaction OB28 to activate the Validation, Click on new entries and enter the following details and save:

CoCd (Company code) = VB15.

CallPnt = 0002 (Line Item).

Validation = VB15_V2

Activtn level = 1(Active).

Now Test if the validation created will trigger. Go to Transaction FB01 and try to create a vendor credit memo(With One vendor Line item: Posting Key : 21)

5. Since we have created a validation rule to trigger for company code: VB15 and only for the vendor Line item (KOART = K), the error message is displayed as below.

Defining Asset Number Range

2011-08-26T05:12:00.001-07:00

Asset Number ranges are defined in the transaction AS08. Go to transaction AS08.

Enter the Company code and click on Intervals. Following screen appears:

As per the client requirement, we can define new number range numbers.

Now, we need to assign the number range number to asset class.

Go to transaction OAOA.

Double-click on any class.

As highlighted above, the number range has to be assigned to the Asset class.

Steps to configure Document text in Customer Invoice Entry (FB70) transaction

2011-08-26T05:11:00.000-07:00

This article shows how to configure document header text in FB70 transaction. It uses the same text determination techniques.

Problem Statement or Requirement Details:

In transaction FB70 which is used to post Customer invoice documents, the client needs a new text id to capture the Vessel Name.

Standard SAP does not provide a screen exit for this transaction which could be used to enhance the std screen to capture the additional data in FB70 transaction.

Solution provided was to create a new document text id which can be configured in the system. This text id can be used to store the Vessel name in the text which can then be used while printing the layout.

The following screen shot shows the FB70 transaction.

As seen above, there are only three text ids currently. We will configure the third fourth text id which will appear below the “Payment Advice Information” text.

The following steps below will show how to configure the text in SPRO.

Step 1 à Goto SPRO à Financial Accounting à Financial Accounting Global Settings à Document à Document Header à Define Text ID’s for Documents.

As seen from the above screen the 3 text id selected are the ones visible on the FB70 transaction. So if you want to have your own text to be displayed click on the Create button on the application tool bar and create your own text id’s.

In our case we will create a text id with the number 0005.

Select the check box so that this text id is made available in FB70 transaction. Click on the save once done.

Since this is a customizing the system will prompt to create a customizing request.

Now if you go back to the FB70 transaction you can find the new text visible under the Document header text

User can make a entry in this field and save the document.

Click on continue and save the document.

The vessel name is now captured in the Customer Invoice document.

Understanding Lockbox

2011-08-26T05:10:00.000-07:00

Objective of this document is to explain the meaning, purpose, advantages and disadvantages of the lockbox. This document also explains various types of formats that can be used to process the lockbox data.

What is a lockbox?

A company can create accounts called ‘lockbox’ accounts at its bank (or banks) that act as payment collection accounts for customer payments. The company then informs their customers that all open item payments for their accounts must be submitted to one of the established bank lockbox accounts. The bank collects these payments along with the customers’ remittance information that indicates what open items the customer payments intend to clear. Data entry clerks at the bank manually enter the information into an electronic file for transmission to the company to which the lockbox account belongs. These files are typically transferred nightly to the various lockbox owners (companies). The files adhere to one of two standard banking industry transmission formats: BAI, BAI2, EDI820 and EDI 823.

Advantages of Lockbox:

Lockbox process has several advantages. Some of them can be illustrated as under.

Avoid Manual handling of checks
Timely processing of Checks
Easy reconciliation
Reduction of manpower cost
Avoid clearing Errors

What is BAI?

The standards for lockbox transmission files are defined by the Bank Administration Institute (BAI). Founded in 1924, the BAI organization is a partnership composed of its own BAI membership, a Board of Directors, various banking industry advisory groups and a professional staff. The organizational mission is “to help bank administrators achieve high levels of professional effectiveness and to help solve significant banking problems.” Activities include the definition of industry file formats, such as lockbox transmissions. BAI and BAI2 are the two defined lockbox transmission formats, however, BAI is considered ‘outdated’ by the BAI organization and is no longer supported (ie. standards are no longer updated or improved). Nonetheless, many banks still offer transmissions in the old BAI format.

BAI vs. BAI2?

BAI and BAI2 formats differ in their level of information detail. BAI does not separate out the incoming check line items by invoice subtotal reference. Instead, one check total amount simply has all invoices listed underneath it. Thus, in BAI format files, the entire check amount must match perfectly (or within configured payment difference tolerances) the total amount for all invoices listed. Otherwise, the entire check will enter into SAP as:

an “On account” posting (if the payment and invoice totals don’t match), or
An “Unprocessed” posting (if no customer account and documents could be identified from the transmission).

In these scenarios, your Accounts Receivable cash application clerks will have to perform manual application to clear payments against open items on the proper accounts.

Conversely, BAI2 splits the check total into separate invoice references and associated payment amounts. Thus, within a large batch, BAI2 format files will allow a “Partially applied” status in which some identifiable payments within the check total will be matched and cleared, others will land on account. As a result, your ‘hit rate’ percentage of payment-invoice matching from each transmission is likely to be higher when using BAI2 rather than BAI formats.

Electronic Data Interchange:

Network transfer of structured electronic data from one computer application to another using standard message formats. EDI is described as the interchange of structured data according to agreed message standards between computer systems by electronic means. This standard format is nothing but a Set of rules, agreed upon, accepted, and voluntarily adhered to, by which data is structured into message formats for exchange of business and operational information. Lockbox related formats are Edi 820 and 823.

EDI 820:

The 820 Payment Order/Remittance Advice transactions can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice. The 820 transaction can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee’s accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.

EDI 823

The 823 Lockbox formats are sent by bank as confirmation of payments received from customers of lockbox owner. EDI 823 format contains information like Bank details of lockbox service provider, total quantity of checks in each format transmission, total amount involved in total checks, number of batch involved ( batch represents maximum quantity of checks in each lot). Further break up like, customer name, customer bank routing number, customer bank account number, check number and amount, number of invoices paid, amount per invoice, discounts for each invoice, deductions if any involved and credit memos etc.

Information available in these formats are generally used for clearing customer open items in SAP depends upon the business requirement. Following EDI configuration is required to read the data from corresponding format and process customer open items.

Format

Idoc type

Message type

Process code

EDI 820

Pexer2002

REMADV

REMA

EDI 823

FINSTA01

LOCKBOX

LBX

Difference between EDI 820 and 823:

In general EDI 820 formats will be used to send information to Vendor furnishing details of payment for his supplies. From business standpoint, EDI 820 information comes from customer as the business is vendor to its customer. In fact EDI 820 is not a lockbox format but can be used in place of lockbox for customer open item processing. This information however is not a real payment but only a remittance advice.

Where as lockbox format is an exclusive format that comes from bank confirming the payments received from customer. This is real payment information which got credited in business account at Lockbox /Bank. Besides this basic difference between these two formats some other differences can be summarized as under.

EDI 820 will have one to one information. Each customer will send remittance information to the business. EDI 823 format will have several customer information in one format.
Customer can not use EDI 823 format where as Bank can use EDI 820 format.
EDI 820 is only an advice but 823 is a payment.
Technical settings viz., Partner profiles, Basic type, Message type, function modules used in SAP are different between these two.
Level of information will be different. EDI 823 will have Total number of checks involved, total payment amount involved, break up of checks and amount per batch, per customer etc will not be available in case of EDI 820.

BAI vs. EDI in Lockbox:

Both the formats are acceptable and can be used in SAP for processing customer open items. However the earlier one is (BAI) is file based and the later format is (EDI) is idoc based. File based is batch mode and EDI is real time information. BAI can not be made as real time process but EDI can be made as batch process.

EDI technology requires mapping tool. It creates intermediate document holding the information for further process. On the other side BAI format doesn’t require this.

As far as processing and of clearing customer open items in SAP is concerned, whether the format is BAI or EDI system will follow same transactions. FB01 > FBE1 > FB05. In either of the case if information is not sufficient to clear open items, it is available for manual process.

Some additional advantages of EDI are:

Data Accuracy
Reduce Technical Complexity.
Lowe Personnel needs.
Accelerates information exchange.
Avoid Data Entry Errors.

Lockbox Process - Data file to SAP open item clearing

What Bank will do?	Bank Receives the payments, create a data file of the customer remittance information and payment amounts, and deposit the checks into client bank account. On regular basis, Client company receives this data file for processing to update in their accounts.
What lockbox data file contain?	Depending upon the choice of services with the Bank, the lock box file will contain information viz., Customer name, Customer Number, Customer MICR number ( Bank routing and Account Number), Check amount, Invoice number, Payment date, Payment amounts and other information.
Lockbox Data Flow	As shown in the following picture, customers send their payments to a lockbox. Then bank collects the data and sends (either through EDI 820 and 823 formats) to R/3 users EDI server (standard Process). The server translates the message using as standard EDI interface into an IDOC (Intermediary documents) and sends it to the SAP Server.
What happens in SAP server	Once the message is received and stored in SAP table, a program is clicked (RFEBLB30 or FLBP transaction) to check the information stored in bank statement tables and create payment advices with Payment amount, invoice numbers and customer number.

Payment advice Processing

Matching of customer open items

The lockbox program uses detailed information from the payment advice to automatically search and match customer open items. The document number on the payment advice is matched against the document number in the customer open item file. Therefore, accurate payment data is necessary for automatic clearing to take place.

Payment Advice Status

If the checks were applied or partially applied, the advice is deleted from the system after processing. If the check was unprocessed or placed on account of customer, the advice is kept on file for further processing.

Post Processing

The post process function entails reviewing the status of the checks applied through the lock box function. User must manually clear any checks that were on-account of customer or not applied to customer account.

The Lockbox overview screen details the number of checks in each category. Depending on the status of the check, the user determines what needs to occur to apply checks.

On account: If the bank keyed in the correct invoice number, the Lockbox Import Program posts the payment on account. In the post processing step, you access the payment advice and correct the document number and upon saving the changes, the post process function clears the open item, deletes the payment advice and sets the check status to applied.

Partially Applied: Checks that are partially applied may require further processing. Ex: Check may have paid 5 invoices, but one was in correctly keyed. The first 4 invoices would clear. The payment amount for the 5th invoice would be put on-account and would have to be post processed to clear.

Unprocessed: Any payment that could not be identified either by customer MICR number (check) or the document number would remain Unprocessed. Once the payment is researched and the customer and invoice is identified, it would be applied during post processing.

What configuration needs to be done?

Control Parameters: It determines the import format BAI, BAI2 & ANSI and the types of postings generated by the lockbox program. These control parameters are needed for importing lockbox file sent by bank.

Posting Data: Company code, Bank Information, G/L accounts for posting and clearing, document types and Posting keys.

RFEBLB30 or FLBP transaction

Lock Box data, Processing parameters (Procedure & Algorithm) Account assignment (Profit center), output control and Mode of call transaction.

Information on FICA (Finance and Contract Accouting)

2011-08-26T05:09:00.000-07:00

The term FI-CA stands for “Contract accounts receivable and payable.“ FI-CA contains the range of functions needed by different industries or projects for their accounts receivable and payable management. Currently, these industries include public sector, utilities and telecommunications companies.
The common factor among these companies is a multitude of customers, which means even more open items. The number of customers in each system may go into the millions, and the number of open items several times that.
Such volumes of data can be processed by FI-CA because the memory space required for storing open and cleared items was reduced and critical activities such as posting, paying, dunning and returns processing were accelerated.

The FI-CA documents provide for the current account assignments from the following application components:

The general ledger. Here it is the company code, business area, G/L account.
The overhead costs Controlling and the Profitability Analysis (CO-PA). Here it is cost center, order, project, Profit Center, profitability segment.

The documents update FI-CA posting totals which are subdivided according to the account assignments named above. However, because the FI-CA documents often only differ from each other with regard to amount, business partner and contract account, a large summarization effect arises in the FI-CA posting totals. So experience from IS-U shows that several hundred thousand FI-CA document items meet on a few hundred totals records.
The FI-CA posting totals form the basis for generating G/L documents, via which not only the general ledger, but also, by transferring the corresponding Controlling account assignments, the different areas of Controlling are updated.
In addition to the account assignment characteristics of G/L accounting and Controlling, the FI-CA posting totals can be grouped according to a freely definable reconciliation key.
This reconciliation key is stored:

• in the FI-CA document header
• in the FI-CA posting totals
• in the document header of the general ledger document as external reference

This makes it possible to understand from which FI-CA documents a general ledger transfer document has been formed. This is a way in which, for instance, a reconciliation between contract accounts receivable and payable and the general ledger for a complete payment run, billing run or a given pile of FI-CA documents can be executed.
The FI-CA documents provide for the current account assignments from the following application components:

• The general ledger. Here it is the company code, business area, G/L account.
• The overhead costs Controlling and the Profitability Analysis (CO-PA). Here it is cost center, order, project, Profit Center, profitability segment.

Integration

The documents update FI-CA posting totals which are subdivided according to the account assignments named above. However, because the FI-CA documents often only differ from each other with regard to amount, business partner and contract account, a large summarization effect arises in the FI-CA posting totals. So experience from IS-U shows that several hundred thousand FI-CA document items meet on a few hundred totals records.
The FI-CA posting totals form the basis for generating G/L documents, via which not only the general ledger, but also, by transferring the corresponding Controlling account assignments, the different areas of Controlling are updated.
In addition to the account assignment characteristics of G/L accounting and Controlling, the FI-CA posting totals can be grouped according to a freely definable reconciliation key.
This reconciliation key is stored:

• in the FI-CA document header
• in the FI-CA posting totals
• in the document header of the general ledger document as external reference

This makes it possible to understand from which FI-CA documents a general ledger transfer document has been formed. This is a way in which, for instance, a reconciliation between contract accounts receivable and payable and the general ledger for a complete payment run, billing run or a given pile of FI-CA documents can be executed.

It is thus in a way a subledger of FICO. FI-CA, though not a complete subledger accounting system, it is always a component of an industry solution or a project solution.

FI-CA is first and foremost a component of the following industry solutions:

• Utilities (IS-U)
• Insurance (IS-IS/PP)
• Public sector (IS-PS)
• Tele communication (IS-T)

FI-CA mainly covers the functionality of those areas in which at least two of the industries reveal the same type of requirements. Individual requirements from exactly one industry are to be achieved as an industry solution on the basis of the FI-CA.

CAREER ABAP

Day 1

Delete PM Notifications

Best Computer Training in SAP ABAP in Hyderabad

Address:#31, 2nd FloorGayatri NagarAmeerpet, Hyderabad -500016Landmark: Behind Huda CenterMobile:8142813133Email-id: sap.invent.it@gmail.com

Business Details for Invent - IT in Ameerpet, Hyderabad

Additional Information for Invent - IT in Ameerpet, Hyderabad

Customer Relationship Management (CRM),

Difference between EEWB and BDT

Difference between EEWB and BDT

Configurations for opening an external URL (like SAP.COM) from IC WebClient.

Configurations to open an external url (like SAP.com) from IC WebClient

Adding Web URL (like google.com, yahoo.com) in CRM UI

Creation and Configuration of Business Partners

Introduction

Objectives

Business Partner

Defining Groupings

Use

Action Profiles in SAP-CRM

Production Planning (PP)

Types of Subcontracting

Difference between Co-Product and Bi-Product with an example

Converting Planned Orders to Purchase Requisitions and Purchase Orders

Routing Vs Task list Vs Work Procedure

Production Order Splitting

Repetitive Manufacturing Cycle

Typical Production cycle in Process Industry

MRP Run in background for all Network Plants

SAP Financials (FI)

Check duplicate creation of Vendor Master that have the same address data through standard SAP settings

Validation rules in FI

Creating a Validation:

Defining Asset Number Range

Steps to configure Document text in Customer Invoice Entry (FB70) transaction

Understanding Lockbox

Information on FICA (Finance and Contract Accouting)

Address:
#31, 2nd Floor
Gayatri Nagar
Ameerpet, Hyderabad -500016
Landmark: Behind Huda Center
Mobile:
8142813133
Email-id: sap.invent.it@gmail.com