please let me know about scripts,idocs,reports,batch job running, work flow

[Former Member]

please let me know about idocs,batch job running,reports,scripts,

usermanuals, and please send me one model standard functional template,

functional spec,landscape, R/3 structure, transport objects,

please send to mail address bvsrc_sekhar@yahoo.co.in

[Former Member]

Hi Chandra Sekhar,

First welcome to this Forum.

Please find the Important stuff below related to your thread.

IDOCS:

IDOCS are intermediary documents which are like CARRIERS of the data.

IDOCs are safe to transfer data, but less volume of data. User is not allowed to access (modify) the data like PSA. IDOCs have 3 parts.

1. Control Record - SOURCE & TARGET details,

2. Data Record - Here comes your query....

Info IDOC - It contains all the technical details related to the data load i.e. Request NO, No of Data Packages, USER, DATE, TIME, LOGICAL SYSTEM, etc. Info IDOC is also ONE segment, the 1 sr segment.

Here data will not be there.

Data IDOC - These are the ones which hold the data. The total no of records are made into Data IDOCs i.e. if 99 records are there then 99 Data IDOCs will be there and all these will be divided into 99 segments.

Hence the total number of Segments in IDOC is 100.

Info IDOC + Data IDOCs = Total no of Segments

1 + 99 = 100.

3. Status Record - Here the status of the data transfer will be available.

ALE:

ALE is Application linking & enabling which enables to interface SAP with other modules.

ALE is used for communicating between sap systems to sap system.

Pl go through below links as they provide all the required info on ALE & IDOC's:

ALE / IDOC:

ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.

ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.

ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.

The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.

ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.

Please check this online document for ALE and IDoc.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

Also check this links for additional information.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

u will have enough material from above .....

Mostly SD consultant doesn’t deal with EDI, Idocs but it’s always good to have knowledge,

EDI

EDI is used to communicate between non sap system to sap system vice versa.

EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.

If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every time send a change to the existing order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).

So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, and INVOIC.

That's all concerning the SD-EDI.

Additional processes in SD, where EDI are used:

1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS

2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD

3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT

4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.

It is all processes which are realized in the SD module via EDI.

Go through this, You will get better idea on EDI,ALE,IDOCS

The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.

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.

While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.

SD REPORTS

Reports: Reports consist of data, which is expected to be reveiwed or checked the transaction taken in said period. Reports are useful for analysis of decision taking for future activities.

Some of the standard reports for SD & its configuration guide is as under:

Standard SAP SD Reports:=

Statistic Group:

Purpose – To capture data for Standard Reports, we require to activate Statistic Group as under:

--> Item category (Configuration)

--> Sales document type (Configuration)

--> Customer (Maintain in Master data)

--> Material (Maintain in Master data)

When you generate statistics in the logistics information system, the system uses the combination of specified statistics groups to determine the appropriate update sequence. The update sequence in turn determines for exactly which fields the statistics are generated.

Configuration:

IMG --> Logistics Information System (LIS) --> Logistics Data Warehouse --> Updating --> Updating Control --> Settings: Sales --> Statistics Groups -->

1. Maintain Statistics Groups for Customers

2. Maintain Statistics Groups for Material

3. Maintain Statistics Groups for Sales Documents

4. Assign Statistics Groups for Each Sales Document Type

5. Assign Statistics Groups for each Sales Document Item Type.....

All Standard Reports which are available are as under:

SAP Easy Access: Information Systems -> Logistics -> Sales and distribution ->

1. Customer -> Incoming orders / Returns / Sales / Credit memos / Sales activities / Customer master / Conditions / Credit Master Sheet

2. Material -> Incoming orders / Returns / Sales / Credit memos / Material master / ...

3. Sales organization -> Sales organization / Sales office / Sales employee

4. Shipping point -> Deliveries / Returns

5. SD documents -> Orders / Deliveries / Billing documents ...

& so on.

Some of the Standard reports in SD are:

Sales summary - VC/2

Display Customer Hierarchy - VDH2

Display Condition record report - V/I6

Pricing Report - V/LD

Create Net Price List - V_NL

List customer material info - VD59

List of sales order - VA05

List of Billing documents - VF05

Inquiries list - VA15

Quotation List - VA25

Incomplete Sales orders - V.02

Backorders - V.15

Outbound Delivery Monitor - VL06o

Incomplete delivery - V_UC

Customer Returns-Analysis - MC+A

Customer Analysis- Sales - MC+E

Customer Analysis- Cr. Memo - MC+I

Deliveries-Due list - VL04

Billing due list - VF04

Incomplete Billing documents - MCV9

Customer Analysis-Basic List - MCTA

Material Analysis(SIS) - MCTC

Sales org analysis - MCTE

Sales org analysis-Invoiced sales - MC+2

Material Analysis-Incoming orders - MC(E

General- List of Outbound deliveries - VL06f

Material Returns-Analysis - MC+M

Material Analysis- Invoiced Sales - MC+Q

Variant configuration Analysis - MC(B

Sales org analysis-Incoming orders - MC(I

Sales org analysis-Returns - MC+Y

Sales office Analysis- Invoiced Sales - MC-E

Sales office Analysis- Returns - MC-A

Shipping point Analysis - MC(U

Shipping point Analysis-Returns - MC-O

Blocked orders - V.14

Order Within time period - SD01

Duplicate Sales orders in period - SDD1

Display Delivery Changes - VL22

FUNTIONAL SPEC:

Q. Please let me know about the Functional spec? How we write the Functional spec?

A. Basically it will be prepared for all New Enhancements that comes in the project.

it consists of the Project Details and the person how prepared in the front page.

As a functional consultant we have to understand the requirement from the client and based on that we have to prepare this functional Spec. Later Functional Consultant will forward the same to the Technical Team to add their comments called Technical Spec, in which the Abapers will give the Technicality of the Requirement in the same and finally it will be sent to Client for Approval.

Functional specification: The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functionality.. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.

The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.

Check this link to know more about functional specifications

To speak at macro level that is at project manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functionality.. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.

The Functional Specification defines what the functionality will be of a particulate area that is to be precise a transaction in SAP terminology.

The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.

The functional specification translates the Software Requirements template into a technical description which

a) Ensures that the product feature requirements are correctly understood before moving into the next step that is technical development process.

b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.

At the consultant level the functional spects are preapred by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.

Let me throw some light on documentation which is prepared before and in a project:

1) Templates

2) Heat Analysis -

3) Fit Gap or Gap Analysis

4) Business Process Design

5) Business Process Model

6) Business Change & Impact

7) Configuration Design, which is just 5 % of Total SAP- have different names -

😎 Future Impact & Change Assessment

9) Functional Design (Module Wise)

10) Risk Assessment

11) Process Metrics and Many More-- Which has impact on Business and its work flow

http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm

http://www.epri.com/eprisoftware/processguide/funcspec.html

Please Reward If Really helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

HI SENT MAIL