Monday, 11 April 2016

Questions and answers

What is the difference between company and company code?
A company is the organizational unit used in the legal consolidation module to roll up financial statements of several company codes. The Company Code is the smallest organizational ! unit for which a complete self-contained set of accounts can be drawn up for purposes of
external reporting.

How many chart of accounts can be attached to a company code?
One or more Operative Chart of Accounts can be assigned to a company code.
A
COA must be assigned to a company code. This COA is the operative COA
and is used in both FI and CO. One Chart of Account can be assigned to
many Company codes i.e., Multiple company codes can either share the
same or have separate COA. But a company code (Country specific Company
code or International Company code) can have a country specific COA
also along with Operative COA. The link between the regular COA and the
country COA appears in the alternate number field of the G/L master
record.
Eg: If a company’s subsidiaries are located in both US
& Mexico. We need to configure 2 Company codes – one for US and
another for Mexico,for eg U100 and M100. The same way we create 2 COA’s
one for US & one for Mexico, USCA and MXCA. Mexico has different
govt reporting requirements than the US so we will need to define a
company code specific to Country Mexico and also create a country
specific COA to be used, in addition to normal COA. In tcode OBY6(Comp
Code Global Parameters) of CC M100 we define normal COA i.e.,USCA in
Chart of Accounts field and MXCA in Country Chart/Accts field.


What are substitutions and validations? What is the precedent?
Validations are used to check settings and return a message if the prerequisite check condition is met.
Substitutions are similar to validations; they actually replace and fill in field values behind the scenes without the user’s knowledge unlike validations that create on-screen msgs to the user.


What is a controlling area?
The Controlling Area is the central organizational unit within CO module. It is representative of a contained Cost Accounting  where costs and revenues can be managed.


Define relationship between controlling area and company code?
A controlling area may include one or more company codes which must use the same operative chart of accounts as the controlling area. A Controlling Area can contain multiple company code assignments but a single company code can be assigned to only one controlling area.

Thursday, 7 April 2016

Summary On IDOC

Summary of IDOC.
The Idoc interface allows the exchange of business data between SAP applications and external systems. The formats used for transmitting data (Idoc types)are documented.
Idocs are exchanged with external systems on a partner-specific and message-specific basis. Idoc data flow is therefore defined via the partner profiles and port definitions.
In outbound processing, Idocs can be collected in a group or sent to the external system immediately.
In Inbound processing, Idocs can be processed via workflow.
Exception handling for incorrect Idocs always takes places via workflow.
Monitoring programs and statistics programs are available for the Idoc data flow. Active monitoring can be used to automatically notify the agent responsible.
Idocs which have been processed completely can be archived.
If the Idoc types in the standard system do not meet your requirements, you can add upwardly compatible extensions or define your own Idoc types.
 
 
IDOC - idoc: Repair and check programs Basis - ALE Integration Technology
WE02 - Display idoc Basis - ALE Integration Technology
IDX2 - Meta Data Overview in idoc Adapter Basis - ALE Integration Technology
IDX1 - Port Maintenance in idoc Adapter Basis - ALE Integration Technology
WE30 - idoc Type Development Basis - ALE Integration Technology
WE05 - idoc Lists Basis - ALE Integration Technology
SXMB_MONI - Integration Engine - Monitoring Basis - Integration Engine
SM59 - RFC Destinations (Display/Maintain) Basis - RFC
SM58 - Asynchronous RFC Error Log Basis - RFC
WE20 - Partner Profiles Basis - ALE Integration Technology
WE19 - Test tool Basis - ALE Integration Technology
BD87 - Status Monitor for ALE Messages Basis - ALE Integration Technology
WE21 - Port definition Basis - ALE Integration Technology
WE31 - Development idoc Segment Basis - ALE Integration Technology
WE82 - Assign Messages for idoc Type Basis - ALE Integration Technology
RBDMIDOC - Variant for RBDMidoc Basis - ALE Integration Technology