cancel
Showing results for 
Search instead for 
Did you mean: 

answers plz

Former Member
0 Kudos

Hi

i have confusion

1) what is check table and what is value table?

2) where we can use check table and value table?

3) please give the business senario of SD and FI/CO?

4) what is ALE and what is IDOC?

plz give the answers

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi,

Difference between a check table and a value table

Value Table

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator. Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . To be maintained as a customization object. This mean that if you want to enter values to this table you have to create a development request & transport the same.

Check table

For example you have Employee master table & Employee Transaction table.

When ever an employee Transacts we need to check whether that employee exists , so we can refer to the employee master table.

This is nothing but a Parent & Child relationship . Here data can be maintained at client level , no development involved.

As per DBMS what we call foregin key table, is called as check table in SAP.

There is 1 more important Difference in Value Table and Check Table is that:

1. The contents of the check will be used as an input help(F4 Help) for a particular field on which a check table is assigned.

But the contents of Value Table are never used in Input Help.

The Heirarchy which decides from where to used the Input Help is:

1. Input help defined explicitly in ABAP Program or Dialog Module.

2. Input Help Attached to the referenced Database Table field.

3. Using the contents of Check Table as an input help if neither (1) or (2) help are there.

4. Input help from Fixed value or Value range given in Domain.

ALE

Application Link Enabling (ALE) is a mechanism for the exchange of business data between loosely-coupled R/3 applications built by customers of SAP, the enterprise resource management program. ALE provides SAP customers with a program distribution model and technology that enables them to interconnect programs across various platforms and systems.

There are three layers in the ALE system: application services, distribution services, and communication services. The vehicle for data transfer is called an IDoc (intermediate document), which is a container for the application data to be transmitted. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system. If the data is distributed from a master system, the same transaction performed by the sender will be performed by the receiving system, using the information contained in the IDoc.

Changes made to fields in master data tables can be set to trigger distribution of the changes to slave systems, so that multiple database servers can update the same information simultaneously. IDocs carry information directly between SAP systems. In order to communicate with a non-SAP system, an IDoc is first transmitted to an intermediary system that translates the data to a format that will be understood by the receiver. Return data also passes through the translating system, where it is again encapsulated into an IDoc.

IDOC

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

for Business scenario please reffer the follwoing links it might help you

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef...

http://help.sap.com/bp_biv170/documentation/SolutionScope_EN.doc

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/sd%2bconfiguration

*********please reward points if the information is helpful to you**********

Former Member
0 Kudos

Hi Krishna

1)check table is primary key table which generates foreign key fields.

value table becomes as a check table when a foreign key is defined,but

value table domain should have foreign key relation ship.

2)value table is defined in domain definition.when u define value

table it checks for check table.

we can define check table in foreign key ralation ship.

3) check this link

http://www.angelstarsix.com/seminar.html

http://www.allinterview.com/showanswers/5379.html

4) Enterprises are increasingly looking to deliver real business benefits by integrating their systems and processes both within their organizations and between organizations. ng processes in this way, which requires tight integration, frequent communication and data exchange.

Highly integrated and inter-dependent SAP and non-SAP systems require frequent communication, tight integration and (usually) high levels of data exchange. In order to achieve this interoperability, SAP has come up with the concept of ALE (Application Linking and Enabling).

The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP com

ge of business information across SAP and non-SAP systems. Applications are integrated by using synchronous and asynchronous communication without implementing a central database.

<b><u>IDOCS</u></b>

IDocs (Intermediate Documents) are the crux of ALE. These are the documents with the help of which data is exchanged between SAP R/3 and non-R/3 systems. As the name suggests, these documents act as intermediate storage of information, which can be sent bi-directionally. Message types are responsible for creation of Idocs.

Reward all helpfull answers

Regards

Pavan

Answers (5)

Answers (5)

Former Member
0 Kudos

ok, That rewarded points will help us to boost

Rewards

Pavan

Former Member
0 Kudos

1. what is check table and what is value table

Check Table:

Check table will be at field level checking.

The ABAP Dictionary allows you to define relationships between tables using foreign keys . A dependent table is called a foreign key table, and the referenced table is called the check table. Each key field of the check table corresponds to a field in the foreign key table. These fields are called foreign key fields.

Value Table:

Value table will be at domain level checking eg: scarr table is check table for carrid.

Prior to Release 4.0, it was possible to use the value table of a domain to provide input help. This is no longer possible, primarily because unexpected results could occur if the value table had more than one key field. It was not possible to restrict the other key fields, which meant that the environment of the field was not considered, as is normal with check tables.

In cases where this kind of value help was appropriate, you can reconstruct it by creating a search help for the data elements that use the domain in question, and using the value table as the selection method.

2. what is IDOC

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

3. what is ALE

SAP has provided ALE (Application Link Enabling) as the solution to these issues. It allows you to:

a. distribute your applications across several SAP systems, such that centralized functions, as well as decentralized functions can operate in the same company arena

b. maintain and distribute master data elements from a central system, thus maintaining unique number ranges across several systems

maintain and distribute control data objects from a central system, thus synchronizing important configuration data. This is important when trying to decentralise functions, yet keep them integrated

couple R/2 and R/3 systems, in some instances

couple SAP and external systems, via IDocs (Intermediate documents) and an external translation mechanism

4. business senario of SD and FI/CO

The FI CO(Financial Accounting) Module integrates with other SAP Modules such as MM (Materials Management), PP (Production Planning), SD(Sales and Distribution), PM (Plant Maintenance),and PS (Project Systems).

The FI Module also integrates with HR(Human Resources) which includes PM(Personnel Management), Time Management, Travel Management, Payroll.Document transactions occurring within the specific modules generate account postings via account determination tables.

SD module basically aims at check automatically the availability, accurate results in increasing customer satisfaction and tight integration wiht PP, MM Stock requirements list provide up to date info about planned production, inventory, sales demand Manage quality certification to clientsDelivery due lists : no more trouble through lost papersMaterial is committed for sureInvoice is related to shipping.

Former Member
0 Kudos

Hi Krishna

If your problem ha s resolved then assign points and close your thread plz

Regards

Pavan

Former Member
0 Kudos

Ok sorry

I'll reward know

Former Member
0 Kudos

HI Krishna,

<b>1 Ans :</b> check table comes from data element level and value table comes from domain level...

<b>3. Ans</b>

SD :

enquary -> quotaion - > sales order -> delivary -> billing -> invoice..

Sorry no idea. on FI/CO.

<b>4.Ans</b>

GO through this site :http://idocs.de

Ok

<b>reward points if helpful,

Regards

Raghunath.S</b>

Former Member
0 Kudos

thank you my problem is solved

Former Member
0 Kudos

hi,

Check Table is for Field level Validation whereas Value table is for Domain Level Validations.

Value Table proposes table for check table.

I think you are clear with this.

more elaborate.

**************************

Check Table

The Check Table is the table used by system to check if a data exist or not exist.

While creating a table if you want to be sure that a field can have some values

and these are in a certain table, you can give IT this table as CHECK TABLE.

Value Table

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator.

Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . .

To be maintained as a customization object.

This mean that if you want to enter values to this table you have to create a development request & transport the same.

Differences:

1)check table will carry out the check for input values for the table field being entered in any application

and value table will provide values on F4 help for that table field.

2)The check table defines the foreign keys and is part of the table definition.

The value table is part of the domain definition.

SD FLOW

SD Flow Cycle:

INQUIRY ( VA11)

|

QUOTATION (VA21)

|

PURCHASE ORDER (ME21)

|

ORDER CONFIRMATION (VA01)

|

PICKING LIST – (VL36)

|

PACKING LIST - (VL02, VL01)

|

SHIPPING – (VT01)

|

INVOICE – (VF21, VF01)

|

AR

Enquiry - Customer enquires about the Products services that were sold by a company - VA11

Quotation - Company Gives a Quotation for the products and Services to a Customer

Sales Order - Customer gives a Purchase order to the company agaionst which a Sales order will be raised to Customer in SAP.

VBAK: Sales Document(Header Data) (VBELN)

VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)

Enquiry, Quotation, Sales Order are differentiated based on Doc.

Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,

for Quotation 'B' & for Order it is 'C'.)

Delivery(Picking, Packing, Post Goods Issue and Shipment)->

Company sends the material after picking it from Godown and Packing it in a Handling Unit(box) and Issues the goods

LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)

LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)

(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)

Billing - Also company bills to the customer for those deliveries

And in FI against this billing Accounting doc is created.

VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)

VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)

(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)

Apart from these tables there are lot of other tables which starts with

‘V’, but we use the following tables frequently.

VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)

VBTYP= ‘C’(Sales Order) VBTYP=’J’(Delivery) VBTYP=’M’(Invoice)

VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)

VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)

VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)

VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)

VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)

VEDA: Contract Data(VBELN,VPOSN)

VEDAPO: Contract Data(VBELN,VPOSN)

KONA: Rebate Agreements (KNUMA,VKORG,VTWEG,SPART)

Refer the link : http://www.sap-img.com/, this might help for FI/CO flow

ALE Integration Technology

Purpose

The integration technology Application Link Enabling (ALE) is an important middleware tool in SAP's Business Framework Architecture (BFA). BFA is a component-based architecture enabling software components from SAP and from other software vendors to communicate and be integrated with each other.

ALE can integrate business processes between R/3 Systems and non-R/3 systems as well as between R/3 Systems.

Data is exchanged between applications and remains consistent in all applications.

Company-wide applications such as accounting, human resource management and sales planning may be carried out in the company’s headquarters, whereas production and materials management may be carried out in decentralized plants.

Application systems are loosely coupled in an ALE integrated system. Data is exchanged asynchronously, whereby the data arrives in the receiver system, even if the receiver system cannot be connected to at the time the data is sent. ALE uses synchronous communication for reading data only.

ALE provides administration, development and testing tools.

-


IDOC

Defining New IDoc Types

Purpose

If the IDoc types (basic types) supplied with the standard SAP System do not meet your requirements, you can define your own IDoc types.

Prerequisites

Before you define a new IDoc type, you should first check whether the basic types can be made to meet your requirements. You can display a list of the basic types and their meaning using the documentation tools in the IDoc Interface.

Process flow

REFER FOLLOWING LINK

http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm

Reward points if it found helpful.

Regards

Former Member
0 Kudos

hi.

Difference between a check table and a value table

Value Table

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator. Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . To be maintained as a customization object. This mean that if you want to enter values to this table you have to create a development request & transport the same.

Check table

For example you have Employee master table & Employee Transaction table.

When ever an employee Transacts we need to check whether that employee exists , so we can refer to the employee master table.

This is nothing but a Parent & Child relationship . Here data can be maintained at client level , no development involved.

As per DBMS what we call foregin key table, is called as check table in SAP.

There is 1 more important Difference in Value Table and Check Table is that:

1. The contents of the check will be used as an input help(F4 Help) for a particular field on which a check table is assigned.

But the contents of Value Table are never used in Input Help.

The Heirarchy which decides from where to used the Input Help is:

1. Input help defined explicitly in ABAP Program or Dialog Module.

2. Input Help Attached to the referenced Database Table field.

3. Using the contents of Check Table as an input help if neither (1) or (2) help are there.

4. Input help from Fixed value or Value range given in Domain.

MM flow is processing between business organisation and Vendor:

1...Purchase Requisition --- T.code ---ME51

2...Source List -


T.code-----ME41

3...Request for Quation (RFQ)-T.codeME21N (To Vendor)

4...Purchase Order -


T.code -


ME21N (To Vendor)

5...Goods Receipt-------T.code....MIGO

(Tables: MKPF, MSEG)

6...Invoice Verification----T.code...MIRO

(Tables: BKPF , BSEG)

7...Vendor Payment----T.code...FB60 (FI - Account Payable)

Document Flow in Sales

The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.

Reward all helpfull answers.

Regards.

Jay