BW configuaration documents

Hi...I am new to BW..Can any one of you please send me the detailed configuartion documents for R/3 and BW side. Like how exactly we should start a project from intial stage configuaration in R/3 side and BW side..Please send me some kind of PPT / step by procedures to understand better.
Appreciate you help. Thanks.
BW Learner.

Hi
Please go through following Links which gives detail info @ Configuration settings to be done both on R/3 as well as on BI side
1. In R/3 Side : http://help.sap.com/saphelp_nw2004s/helpdata/en/ce/c2463c6796e61ce10000000a114084/frameset.htm
2. In BI Side :
http://help.sap.com/saphelp_nw2004s/helpdata/en/ce/c2463c6796e61ce10000000a114084/frameset.htm
Hope it helps...
Regards
Swapnil.

Similar Messages

MM Blueprint documentation

SAP Gurus,
Please help me in providing the sample Blueprint documention for MM module.I appreciate if you would provide for Automotive company. By seeing that i should get an idea how the documentation is being prepared. I tried searching the forum but i was unable to open the link the specified. Many thanks to you all in advance.

>
Dinsap wrote:
> Arun Guru,
>
> Excellent! Thanks for giving an idea about AS IS blueprint document. I think depend upon the inputs from the client the TO BE Blueprint document will be prepared. right? If not, do we have any standard document for TO BE configuration.
>
> Thanks in advance guru.
>
> Prem
Hi,
Yes u are right. based on the AS IS we ahve to create TO BE blue print documents(Configuaration documents).
Arun

Open Ldap 2.4 is supported

Hello
We want to connect SAP ERP 6.0 to Open Ldap 2.4, I need following
information:
1.Is Opne LDAP 2.4 is supported by SAP ERP 6.0
2.Configuaration documents for same.
Many thanks in advance,

Hi there,
Are you receiving any error messages? Can you confirm that the Cisco DirSync process is started and/or reset and try the sync again. Also, you may want to check to make sure there are no firewalls/ports being blocked between CUCM and your LDAP server.
You'll also want to make sure your LDAP Directory page is mapping attributes correctly to your OpenLDAP server under System > LDAP > LDAP Directory. By default it is set to use sAMAccountName for the UserID field.
Table 16-5 Synchronized LDAP Attributes and Corresponding Unified CM Field Names
Unified CM User Field Microsoft Active Directory Active Directory Application Mode (ADAM)
or Active Directory Lightweight Directory Service (AD LDS)
Netscape, iPlanet, or Sun ONE
OpenLDAP
User ID
One of:
sAMAccountName
mail
employeeNumber
telephoneNumber
userPrincipalName
One of:
uid
mail
employeeNumber
telephoneNumber
userPrincipalName
One of:
uid
mail
employeeNumber
telephonePhone
One of:
uid
mail
employeeNumber
telephonePhone
First Name
givenName
givenName
givenname
givenname
Middle Name
One of:
middleName
initials
One of:
middleName
initials
initials
initials
Last Name
sn
sn
sn
sn
Manager ID
manager
manager
manager
manager
Department
department
department
departmentnumber
departmentnumber
Phone Number
One of:
telephoneNumber
ipPhone
One of:
telephoneNumber
ipPhone
telephonenumber
telephonenumber
Mail ID
One of:
mail
sAMAccountName
One of:
mail
uid
One of:
mail
uid
One of:
mail
uid
HTH,
Chris

Need document for oem installation and configuaration?

Hi,
In my environment our databases are running linux. i want to configurare all database in oem . please guide me
Thanks,

Without Oracle version it's hard to give specific answer.
Try here
Oracle® Enterprise Manager Advanced Configuration
http://download.oracle.com/docs/cd/B19306_01/em.102/b40002/toc.htm

Need help in ALE configuaration !

Please send me an example of how to create an ALE configuaration with in one client !

HI,
What is ALE?
ALE stands for Application Link Enabling and is a remote connection technology allowing the decentralization of business processes by connecting decentralized systems together.
Using ALE, it is fairly easy to synchronize several SAP systems so that they contain the same data objects at anytime. These objects may be master data (customers, vendors, GL accounts, cost centers, ...) or transaction data (FI documents, purchase orders, ...). To enable the synchronization, ALE supports not only mass transfer of data between systems but also selective data transfers of objects changed since the last transfer.
How does it work?
Viewed from a high level perspective, the process is straight and simple: a sender system selects the data that needs to be distributed, packs it in a standard format and sends it to one or several receiving systems. When a receiving system gets the data, it unpacks the standard format and records the data.
In fact, 3 layers are involved in this process:
An application layer which selects and records data in R/3.
A distribution layer which filters and converts data.
A communication layer which ensures the actual communication of records generated in a standard format.
The senders and receivers are determined thanks to a so-called distribution model which defines the transfer rules (who sends what to who?). The definition of the distribution model must be known by all systems involved (either as sender or receiver) and must consequently exist on all those systems.
The Intermediate Document (IDoc)
The data transferred using ALE must have a SAP standard format to be understood from all partners in the communication. This format is the Intermediate Document (IDoc) which represents an intermediary structure between raw SAP data and EDI formats. This structure is not constant, it depends on the data to be transferred and SAP provides the structures for most SAP standard objects such as customers master data, sales orders, ...
An IDoc with a specific structure is said to have a specific type. The IDoc type is nothing more than a version of a specific IDoc structure designed to contain data for a specific object type. For example, the IDoc type DEBMAS05 is the fifth version of a structure that represents a customer master data. The management of versions for IDocs structures is necessary because the objects evolve with time and tend to become more and more complex with new data fields or tables being added regularly.
The conversion of raw data forth (for the sender system) and back (for the receiver system) to the IDoc format is also ensured by SAP standard function modules as long as you transfer standard objects. For non standard objects (enhancements), you must define your own IDoc structure and write your own conversion function modules.
RFC connections
The data communication between the SAP servers may be done by several ways. The 2 most common ways are the transactional RFC and the file. The RFC connection is used to make a direct connection between servers while the file interface speaks for itself, it uses a file containing the IDocs from the sender system as input in the receiver(s) system(s).
The selection of a communication method is made though the ports configuration as we will see in the next section. For the purpose of this article, we are going to choose the most efficient method: the transactional RFC method. To set it up, we first need to define the RFC destinations of the partner systems.
An RFC destination may be seen as a set of settings necessary to connect to a system using the RFC protocol. These settings include the address and type of the partner system along with connection information such as the user ID and password to use.
The RFC destinations of all partners systems must be defined on all systems to include in the distribution model. The transaction to use for this purpose is SM59.
Definition of the communication ports
The communication ports determine the type of data communication that must occur between systems. When the communication is to use the RFC protocol, transactional RFC ports must be created specifying the RFC destinations of the partner systems. Use transaction WE21 for this purpose.
Partners profiles
In SAP, all partners systems involved in a distribution model have a profile. There exist several profile types such as customers profiles, vendors profiles, ... but this distinction between profiles is generally not necessary and you will create in most cases your partners profiles using a generic Logical System type.
Before entering the settings of the logical systems partners, you have to create them in customizing. Also, each system in the distribution model must be assigned in its own system its own logical system that represents it. This assignment is done at client level and not at system level. This is not easy to explain nor to understand so let's take a simple example. Let's consider we have a simple distribution model made up of a sender system (S01) and a receiver system (R01). We need to transfer data from S01 / client 100 to R01 / client 200. In both the systems, we will define the logical systems S01_100 and R01_200. But in sender system S01, the logical system S01_100 will be assigned to the client 100 while in the receiver system R01, it will be R01_200 that will be assigned to client 200. With such a configuration you see it is even possible to transfer data between two clients from the same system.
A partner profile is used to determine a lot of important settings that will be involved in the data transfer. These settings vary depending on the role of the partner system (sender / receiver) and are defined per message type. A message type is more or less a version independent IDoc type. It is mainly a convenient way of defining settings and identifying IDocs using a criterium independent of the partner system.
For a sender partner system (inbound parameters are filled in), following important settings are set per message type in the partner profile:
A process code used to indicate which function module will be used to convert the IDoc data to SAP data.
The time of input of the IDoc: as soon as the IDoc is created in the system or on request (using program RBDAPP01).
The post processing agent who will have to treat the data input errors if need be. The post processing agent may be either a user or any other HR organizational unit.
For a receiver partner system (outbound parameters are filled in), following settings are specified in the partner profile:
The receiver port to which the data will be sent.
The sending method: one IDoc at a time or by packets.
The IDoc type that will be sent to that partner. For a given message type, the IDoc type sent may vary depending on the receiver system. Indeed you may have different versions of SAP in your system landscape.
Definition of the distribution model and data filtering
We have already seen that the distribution model is used to decide who sends what to who. But, as you guessed, there is a little bit more to be said about it and the way to manage it.
The distribution model is maintained in a central transaction (BD64) which lets you access the most useful environmental settings necessary to set up the model. Before creating the model, you must first decide on which system you are going to create it. Indeed the model must exist in all partners systems and two possibilities exist to achieve this.
Either you create the model on each system manually (with the same model technical name), which is feasible only with few systems and/or simple models. Either you create it in a specific system (usually the source system) and distribute it to the other systems thanks to the distribution command in the BD64 transaction menu.
If we want to copy the customers master data from the production system to the other systems in the maintenance line for example, we may create the distribution model on the production system and distribute it to all partners systems.
The actual creation of the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender system, a receiver system and message types to exchange between those systems. You may afterwards add more sending and receiving systems in the model as well as more message types.
For each message type defined between a sender and a receiver, you may set filters on specific fields of the message type so that IDocs be generated only when these specific values are matched. For example, you may decide to send only customers of a specific account group. These filters are set by selecting the 'no filter set' text under message types in BD64.
There exists also another kind of filters which are segments filters. They do not filter IDocs creation based on values like we have just seen but filter unconditionally segments of created IDocs which must be excluded from the transfer (transaction BD56).
This article will help you understand the basics of ALE and IDocs via a simple do-it-yourself example. We will create a custom IDoc in one SAP system and then post some business data through it to another SAP system. Business data will be picked up from custom data dictionary tables.
ALE Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data.
The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Complete documentation on IDOC is obtained by using transaction WE60.
Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of sender/receiver and other control information. Data records contain the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to other.
Now, let us understand the ALE Configuration by means of an example scenario below:
The Scenario
Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system.
Create three tables as shown below.
Creating Custom IDoc type and Message type
All the objects created should be present on both source as well as target system(s).
1. Create segments Transaction WE31
Create a segment ZRZSEG1
Add all fields of table ZCUSTOMERS to it
Save the segment
Release it using the menu path Edit -> Set Release
Similarly create two more segments given below
Seg. ZRZSEG2 to hold all fields of table ZSOHEADERS
Seg. ZRZSEG3 to hold all fields of table ZSOITEMS
2. Create Basic IDoc type Transaction WE30
Create a Basic type ZRZORDER
Add the created segments in the hierarchy shown
Maintain attributes for each of the segments
Save the object and go back
Release the object using the menu path Edit -> Set Release
3. Create/Assign Message type Transactions WE81/WE82
Go to WE81
Create a new Message type ZRZSO_MT
Save the object
Go to WE82 and create new entry
Assign the message type ZRZSO_MT to the basic type ZRZORDER
Also specify the Release Version
Save the object
Thus we have defined the IDoc structure which will hold the data to be transferred. In the [1] next part of the article we will understand the outbound settings, i.e. the settings to be done in the source system.
Outbound Settings
Define Logical Systems and Assign Client to Logical System Transaction SALE
Go to Define Logical System (See the figure)
Define a new logical system to identify the local system and save it
Now, go to Assign Client to Logical System (See the figure)
Add a new entry
Specify the client, previously created logical system and other attributes
Save the entry
Define a new logical system to identify the partner system and save it
Maintain RFC Destinations Transaction SM59
Create a new RFC destination for R/3 type connection
Specify the target host on Technical settings tab
Provide the Logon credentials on the Logon/Security tab
Save the settings
To verify the settings, Click on Test connection or Remote logon
Define Ports Transaction WE21
We need to define a tRFC port for the partner system
Click on Transactional RFC node
Create a new port
Provide a description
Specify the name of the target RFC destination
Save the object
Maintain Distribution Model Transaction BD64
Click on Change
Create a new model view
Provide a Short text and Technical name to the model view
Add message type
Specify sender and receiver systems
Also, specify the message type that we created previously
Save the Distribution model
Generate/Create Partner Profile Transactions BD82/WE20
To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
Otherwise, you may use transaction WE20 to create a partner profile
On selection screen, specify the model view, target system and execute
The result log will be displayed on the next screen
To verify the partner profile go to WE20
Check the partner profile for the target system
Distribute Model View Transaction BD64
Select the Model View
Go to menu path Edit -> Model View -> Distribute
Result log will be displayed on the next screen
Outbound IDoc Generation Program
Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:
Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria
Fill the control record structure of type EDIDC
Specify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver
Fill the data records
Define structures like the IDoc segments
Fill the structures with fetched data
Pass the segment name and the above structure to the appropriate fields of EDIDD type structure
Append the EDIDD structure to the EDIDD type internal table
Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table
Commit work if return code is zero
Function module returns a table of type EDIDC to provide the details about generated IDoc
Display appropriate log
You can [2] download sample code for the above program here.
Thus we have completed sender side configuration required for ALE. In the [3] next part we will see how to configure the receiving system to be able to receive and post the inbound IDoc.
Inbound IDoc Posting Function Module
In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.
Add Include MBDCONWF. This include contains predefined ALE constants.
Loop at EDIDC table
Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception
Loop at EDIDD table
Append data from the segments to appropriate internal tables
For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS
Update the DDic tables from internal tables
Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.
Status 53 => Success
Status 51 => Error
You can [3] download the sample ABAP code for the above function module here.
Inbound Settings
Define Logical Systems Transaction SALE (Please refer to Outbound Settings discussed in [4] previous part)
Assign Client to Logical System Transaction SALE (Please refer to Outbound Settings discussed in [5] previous part)
Maintain RFC Destinations Transaction SM59 (Please refer to Outbound Settings discussed in [6] previous part)
Define Ports Transaction WE21 (Please refer to Outbound Settings discussed in [7] previous part)
Generate/Create Partner Profile Transactions BD82/WE20 (Please refer to Outbound Settings discussed in [8] previous part)
Assign Function Module to Logical message Transaction WE57
Create a new entry
Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT
Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)
Save the entry
Define Input method for Inbound Function Module Transaction BD51
Create a new entry
Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT
Specify the Input method as 2
Save the entry
Create a Process Code Transaction WE42
Create a new Process Code ZPCRZ
Select Processing with ALE Service
Choose Processing type as Processing by function module
Save the entry
On the next screen, select your function module from the list
Save the changes
Now you will be taken to the next screen
Double-click on Logical message
In the Assignment to logical message, specify the message type ZRZSO_MT
Save the changes
Send and receive data
On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.
Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.
Thus to summarize we have learned how to:
*& Report ZRZ_ORDER_IDOC                                              *
REPORT ZRZ_ORDER_IDOC                          .
PURPOSE OF REPORT *
Generats an Idoc for Customer Master, Sales Master
and Sales item table.
TABLES : ZCUSTOMERS, "Cutomer Header
         ZSOHEADERS, "Sales Header
         ZSOITEMS. "Sales Items
DATA : S_CTRL_REC LIKE EDIDC, "Idoc Control Record
       S_ZRZSEG1 LIKE ZRZSEG1, "CUSTOMER Header Data
       S_ZRZSEG2 LIKE ZRZSEG2, "SALES HEADER Data
       S_ZRZSEG3 LIKE ZRZSEG3. "SALES Detail Data
DATA : T_ZCUSTOMERS LIKE ZCUSTOMERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOHEADERS LIKE ZSOHEADERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOITEMS LIKE ZSOITEMS OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE."Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
"Generated Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG1',
C_ZRZSEG2 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG2',
C_ZRZSEG3 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG3'.
CONSTANTS: C_IDOCTP LIKE EDIDC-IDOCTP VALUE 'ZRZORDER'.
Selection Screen
SELECT-OPTIONS : S_KUNNR FOR ZCUSTOMERS-KUNNR OBLIGATORY,
                 S_VBELN FOR ZSOHEADERS-VBELN.
PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZRZSO_MT',
              "Message Type
              C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',
              "Partner type of receiver
              C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'Y901',
              C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000226',
              C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'LSSENDS',
              C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.
"Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_DATA_RECORDS.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*&      Form generate_data_records
FORM GENERATE_DATA_RECORDS .
PERFORM FETCH_ZCUSTOMERS.
PERFORM FETCH_ZSOHEADERS.
PERFORM FETCH_ZSOITEMS.
PERFORM ARRANGE_DATA_RECORDS.
ENDFORM.                    " generate_data_records
*&      Form fetch_zcustomers
FORM FETCH_ZCUSTOMERS.
SELECT *
FROM ZCUSTOMERS
INTO TABLE T_ZCUSTOMERS
WHERE KUNNR IN S_KUNNR.
IF SY-SUBRC NE 0.
    MESSAGE E398(00) WITH 'No Customers Found'.
ENDIF.
ENDFORM.                    " fetch_zcustomers
*&      Form fetch_zsoheaders
FORM FETCH_ZSOHEADERS.
SELECT *
FROM ZSOHEADERS
INTO TABLE T_ZSOHEADERS
WHERE VBELN IN S_VBELN
    AND KUNNR IN S_KUNNR.
IF SY-SUBRC NE 0.
    MESSAGE I398(00) WITH 'No Sales orders found'.
ENDIF.
ENDFORM.                    " fetch_zsoheaders
*&      Form fetch_zsoitems
FORM FETCH_ZSOITEMS.
IF NOT T_ZSOHEADERS[] IS INITIAL.
    SELECT *
    FROM ZSOITEMS
    INTO TABLE T_ZSOITEMS
    FOR ALL ENTRIES IN T_ZSOHEADERS
    WHERE VBELN = T_ZSOHEADERS-VBELN.
    IF SY-SUBRC NE 0.
      MESSAGE I398(00) WITH 'No Sales order items found'.
    ENDIF.
ENDIF.
ENDFORM.                    " fetch_zsoitems
*&      Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = C_MESTYP. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
ENDFORM.                    " generate_control_record
*&      Form send_idoc
FORM SEND_IDOC.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = S_CTRL_REC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = T_COMM_IDOC
      MASTER_IDOC_DATA               = T_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    COMMIT WORK.
    LOOP AT T_COMM_IDOC.
      WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
    ENDLOOP.
ENDIF.
ENDFORM.                    " send_idoc
*&      Form arrange_data_records
FORM ARRANGE_DATA_RECORDS .
DATA: W_INDEX1 LIKE SY-TABIX,
        W_INDEX2 LIKE SY-TABIX.
SORT T_ZCUSTOMERS BY KUNNR.
SORT T_ZSOHEADERS BY KUNNR VBELN.
SORT T_ZSOITEMS BY VBELN POSNR.
LOOP AT T_ZCUSTOMERS.
    S_ZRZSEG1-KUNNR = T_ZCUSTOMERS-KUNNR.
    S_ZRZSEG1-NAME1 = T_ZCUSTOMERS-NAME1.
    S_ZRZSEG1-ORT01 = T_ZCUSTOMERS-ORT01.
    S_ZRZSEG1-LAND1 = T_ZCUSTOMERS-LAND1.
    T_EDIDD-SEGNAM = C_ZRZSEG1.
    T_EDIDD-SDATA = S_ZRZSEG1.
    APPEND T_EDIDD.
    CLEAR T_EDIDD.
    CLEAR W_INDEX1.
    READ TABLE T_ZSOHEADERS WITH KEY KUNNR = T_ZCUSTOMERS-KUNNR BINARY SEARCH.
    IF SY-SUBRC = 0.
      W_INDEX1 = SY-TABIX.
      LOOP AT T_ZSOHEADERS FROM W_INDEX1.
        IF T_ZSOHEADERS-KUNNR NE T_ZCUSTOMERS-KUNNR.
          EXIT.
        ENDIF.
        S_ZRZSEG2-VBELN = T_ZSOHEADERS-VBELN.
        S_ZRZSEG2-KUNNR = T_ZSOHEADERS-KUNNR.
        T_EDIDD-SEGNAM = C_ZRZSEG2.
        T_EDIDD-SDATA = S_ZRZSEG2.
        APPEND T_EDIDD.
        CLEAR T_EDIDD.
        CLEAR W_INDEX2.
        READ TABLE T_ZSOITEMS WITH KEY VBELN = T_ZSOHEADERS-VBELN BINARY SEARCH.
        IF SY-SUBRC = 0.
          W_INDEX2 = SY-TABIX.
          LOOP AT T_ZSOITEMS FROM SY-TABIX.
            IF T_ZSOITEMS-VBELN NE T_ZSOHEADERS-VBELN.
              EXIT.
            ENDIF.
            S_ZRZSEG3-VBELN = T_ZSOITEMS-VBELN.
            S_ZRZSEG3-POSNR = T_ZSOITEMS-POSNR.
            S_ZRZSEG3-MATNR = T_ZSOITEMS-MATNR.
            S_ZRZSEG3-NETWR = T_ZSOITEMS-NETWR.
            S_ZRZSEG3-ZMENG = T_ZSOITEMS-ZMENG.
            T_EDIDD-SEGNAM = C_ZRZSEG3.
            T_EDIDD-SDATA = S_ZRZSEG3.
            APPEND T_EDIDD.
            CLEAR T_EDIDD.
          ENDLOOP.
        ENDIF.
      ENDLOOP.
    ENDIF.
ENDLOOP.
ENDFORM.                    " arrange_data_records

Unable to open DRM protected documents on IPAD

Can Anyone help me for this, my configuaration is as follow -
Adobe Livecycle
Version 10.0.2, GM
Service Pack Version N/A
Patch Version N/A
JBOSS AS
JBoss 4.2.1 for Adobe LiveCycle ES3
Database
SQL SERVER 2008 R2
JDK
jdk1.6.0_26
OS
Windows server 2008 R2 SP1
Adobe Reader ( ipad Ver.)
11.0.1(81383)
Adobe Reader (Desktop Ver.)
Adobe Reader x ver:10.1.9

PDF documents should read easily in the Preview application, or Adobe Acrobat Reader for the Mac:
https://get.adobe.com/reader/
Word and Excel documents can be read by any of these Office clone software titles listed on my tip:
https://discussions.apple.com/docs/DOC-6941
If they don't open, then they probably aren't proper files, or saved by a newer version of the software than you have.

Solution manager configuaration Guide

HI,
As a functional consulatnt ,i want some document to configured the solution manager in system so please provide me document for the same.
so please help me on this and if someone have worked on configuaration of solution manager then please also give me contact number as i have some queries related to this.
Thanks and Regards,
Vivek Garg

hi,
i have worked on solution manager
but, here we will not do any thing we will define our project and basing on your base line configuration or business process you will get the documentation automatically and the source is from liabrary all the diagrams will be taken from the liabrary.
http://help.sap.com/saphelp_sm32/helpdata/en/ae/64c33af662c514e10000000a114084/content.htm
regards,
balajia

What is the pupose of rebate agrrement? configuaration process

what is the pupose of rebate agrrement? configuaration process

Hi Deva,
As he rightly said, you need to understand the basic sd module functionlity, else make a small search in forum.
I dont want to dispoint you this time, going forward do it. For your reference find the complete config process of rebate.
What do you mean by Rebate: - Rebate is a special kind of discount, which is paid retroactively to a customer once he achieves or reaches the sales volumes, in a given period of time.
Rebate agreement: - A Rebate agreement is an agreement between the business and a customer. The rebate is only relevant if the customer purchases the required sales volume. In rebate agreement, you specify who receives the rebate payment and on what criteria rebate is based. Ex. Customer, customer and material etc,.
Rebate agreement type: - The rebate agreement type determines which data the system is to automatically propose for rebate agreement.
Structure:
You can define the following data in a rebate agreement:
     Validity period
     Status (whether the agreement is released for settlement)
     Rebate recipient (the party who receives the credit memo)
     Currency
     Method of payment (cheque, bank transfer etc)
Data Defined In Condition Records:
     Basis for rebate (customer, customer/ material, rebate group, etc)
     Validity period (the validity must lie with in the validity of rebate agreement)
     Cond rate
     Material for settlement
     Accrual rate
     Other control data, such as pricing scale type
Prerequisites for Rebate Processing:
     Sales orgn: must be relevant for rebate processing
     Payer: must be relevant for rebate processing
     Billing type: (invoice, credit memo etc) must be relevant for rebate processing
For performance reasons, you should deactivate rebate processing if it is not necessary.
Material for Settlement: In case of customer rebate where there is no material linked, a dummy material is give as material for settlement.
You may have to create rebates that do not depend on a material, but instead, e.g. on:
     A Customer
     A Customer Hierarchy
     A Group of Materials
You will then need to refer to a material for settlement. The system uses this material when you pay out the rebate. It does not matter which material type & mat application type you use.
When you create the cond record with in the rebate agreement, the system automatically asks you to enter the no of material for settlement.
Manual accruals: Instead of posting accruals from the billing documents, manually we can post accruals through the debit memo. If you activate this field if you want to be able to post manually for this agreement type.
Reverse accruals:- Whatever manual accruals we have given can be reversed through the reverse accruals. Mark this field if you want accruals to be reversed when a manual payment is made for a rebate agreement of this type. The system uses reverses accruals for the amount of the manual payment. If the cumulative accruals are not sufficient, the system reverses the accruals amount, which exists.
Relationship to Pricing
     Rebates differ from other kinds of discounts in that they are based on sales volume over time and are paid retroactively.
     However, the system processes rebates in much the same way as other kinds of pricing elements.
     Rebate data is saved in condition records.
     Controlling for rebate processing is carried out via condition types, pricing procedures and access sequences.
     This control data is defined in Customizing for Sales and Distribution.
Rebate based on Group of Materials:
A rebate group consists of materials to which you want to apply the same rebate. You system administrator can define rebate group in Customizing for Sales according to the need o f the orgn.
You can assign a material to a rebate group in the MMR: view- Sales, field- Rebate Grp. When you create a cond record, you must enter a settlement material.
Rebate Agreement Types:
Agreement Type     Basis for Rebate          Cond Type
0001     Customer / Material     % Rebate     BO01
     Customer / Rebate Group     % Rebate     BO01
0002     Customer / Material      Quantity Dependent     BO02
0003     Customer     Percent rebate     BO03
0004     Customer hierarchy     Percent rebate     BO04
     Customer hierarchy / Material     Percent rebate     BO05
0005     Sales Volume Independent          BO06
SPRO- IMG- SD- BILLING- REBATE PROCESSING:
     Define rebate agreements
     Condition type groups
o     Define cond type groups
o     Assign cond types to cond type groups
     Maintain access sequence
     Define condition types
     Assign conditon types to conditon type groups
     Maintain pricing procedure
o     Assign condition type groups to rebate agreement types
     Activate rebate processing
o     Select billing documents for rebate processing3
o     Activate rebate processing for sales organisations
o     Activate at customer level.
1. Define Agreement Types:
Copy & rename: 0002 & go to Details
     From
     To
     Reverse accruals: flag it on
     Manual Accrual Doc Type:           Doc Type (R4) & Billing Doc Type: B4
     Verification level: payer, material
     Partial payment:               Doc Type (R3) & Billing Doc Type: B3
     Rebate credit memo:               Doc Type (R1) & Billing Doc Type: B1
2. Define Condition Type Groups:
Copy & rename: 0002. Give the same code as given to agreement type.
3. Assign Condition Type to Condition Type Group:
In this activity one needs to assign the cond type from the pricing procedure to the cond type group found on the rebate agreement type. The sequence no column represents the fields in the cond table that determines what the system is to use as the basis for rebate. In this e.g., 1 determines that the cond type should use the fields customer & material. The cond type group 0002 will use pricing cond type BO02. Before assigning cond type to cond type group, you have to create a cond type.
     Cond Technique for rebate processing:
     Create cond table
     Maintain access sequence
     Define cond type: BO02 is the cond type used in pricing, copy & rename.
     Assign cond type to cond type group: BO02 to 0002
     Maintain pricing procedure: assign cond type BO02 to pricing proc, after total discount & before freight. Assign Subtotal: 7, Account Key: ERB, Accruals: ERU (keeping reserve money from customer money), & Requirement: 24 (rebate will get affected in billing doc & not in sales doc)
     The cond type BO02 must use cond class C- expense reimbursement.
     The rebate procedure in BO02: indicates if the cond is dependent or independent of sales volume
     The accruals correction proc indicates if accruals must be corrected when this cond type is accessed.
4. Assigning Cond Type Groups to Agreement Type:
Here you are presented with a list of agreement types as created in the system & you can assign the relevant cond type group
5. Activate Rebate Processing: at the following levels.
     Sales orgn level: activate rebate processing for sales organisations
     Billing Document: select billing doc for rebate processing
     Customer: active rebate in CMD Sales Area Data, Billing Tab Page.
Billing Document Types
F2     Standard Invoice     F1     Order Relate invoice
BV     Cash Sale     B1, B2, B3, B4     Rebate invoices
G2     Credit Memo     L2     Debit Memo
S1     Invoice Cancellation     S2     Cancel Credit Memo
IV     Inter Company Sales
NOTE: - You cannot activate Rebates for Billing document type F5 & F8, since they are proforma invoices.
Create Rebate Agreements: VBO1
Easy Access- Logistics- SD- Master Data- Agreements- Rebate Agreements- Create
Agreement type: 0002 & press enter. In the over view screen fill the following details:
     Rebate recipient: payer no
     Currency
     Validity Period
     Agreement Status: open
     Then Go To Conditions Icon & Fill
     Material, Rebate Amount, Accruals & save
     Then create sales order, delivery, picking, goods issue & invoice
     After this in order to see rebate in sales order cycle Go to: VF01 Go to Conditions (item). You can check rebate in VF01 before saving or else you can also see in VF02.
Rebate Settlement: VBO2
     The system uses the accumulated amounts in the rebate agreement to create a rebate settlement.
     The system generates a rebate credit memo request for the rebate payment amount specified.
     There are 3 statuses available for rebate agreements
1.     Status A refers to an open rebate agreement.
2.     Status B means the rebate is released for settlement.
3.     Status C means you have actually executed the settlement. The System creates a credit memo request for the accrual amount.
     You can display the sales volume and drill-down in the rebate agreement.
     You can carry out a final settlement for the rebate agreement either:
a.     Manually
b.     Automatically
c.     In the background (batch programs: RV15C001 and RV15C002)
     Accruals are reversed as soon as the rebate agreement is settled by credit memo.
Process of Rebate settlement:
     Use VBO2 and type in the agreement Number. Change the Agreement Status to B and click on Final Settlements->Automatic. On doing so, a Credit Memo Request gets created.
     Status is set to C. Save it.
     A credit Memo Request Number is generated.
     Go to VA02 and type in the Credit Memo Request number generated. Remove the Billing Block and Save it.
     Use VA02 to go to Sales Document and Click on Billing. On Saving it, the Credit Memo Request is now Billed
     Go to VBO3 and see the Agreement Status. It would have been set to D, which means that final settlement of agreement has been carried out.
Important:-
1. When you save the rebate agreement, the system will automatically create a credit memo request. The system uses this document to create a credit memo. When the credit memo is released, the accruals are posted to FI.
2. If you have posted accruals manually, but these have not been passed on to financial accounting, the manual accruals and manual payments in the rebate agreement are blocked.
3. The system can use the sold to party or ship to party as we as payer as the rebate recipient. You cannot use alternative partner as the rebate recipient, such as alternative payer for the CMD of the sole to party.
Reward points,
Vamsi P

Error while resetting a cleared document

Hi everyone,
I am getting an error while resetting a cleared invoicing document 'Document xxxxxxxxxxx with origin R4 can not be reversed'. Please guide me how can we reset the clearing of this document.
Thanks and Regards

Hi,
You need to reset all clearing for the corresponding FICA document for the print document.
Reset the clearing for the document no. mentioned in the output for EA13 execution.
You need to reset all the clearing for the document, before reversing the same.
To get all the clearing document, go to DFKKOP table, enter the FICA document no. (for the print document on FPL9). Get all AUGBL documents,
Alternatively, you can go on to FPL9 screen, double click on the consumption document, in the basic data you will see the clearing date (if it is cleared), expand the view their (click on + sign), you will se the clearing document no,
Pass the above clearing document no, to FP07, and once all the clearing is reset for the invoice, you can reverse the corresponding invoice through EA13.
Regards,
Rajesh Popat

Filename in document

Hi all,
Just new to Mac so I've to learn a lot.
How can I insert the filename (semi)automaticly into the document.
I have a template document and save this as .... I want the filename to appear in the document.
Is this possible?? If yes HOW

As far as I know, we are in a forum dedicated to Numbers '09
For Numbers v1.0.2, you take care of what was posted several times:
go to my iDisk:
<http://idisk.me.com/koenigyvan-Public?view=web>
and download for free
For_iWork:iWork '08:forNumbers:paste_thename.zip
and or
For_iWork:iWork '08:forNumbers:paste_thepath.zip
Yvan KOENIG (from FRANCE mercredi 21 janvier 2009 17:56:54)

I can't save downloads to documents folder, only to desktop...

Only desktop saves are allowed. The message states, "Word cannot save or create this file. This disk may be full or write protected..." The disk isn't full, so I'm not sure what to do. I'm having to save everything to the desktop and then move files into document folders in Finder. Any advice on how to save directly to documents or what may be wrong? Thanks so much!.

Back up all data now.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. You can demote it back to standard status when this step has been completed.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Drag or copy — do not type — the following line into the Terminal window, then press return:
sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:20 ~ $_ ; chmod -R -N ~ $_ 2> /dev/null
Be sure to select the whole line by triple-clicking anywhere in it. You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning. If you don’t have a login password, you’ll need to set one before you can run the command.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select Utilities ▹ Terminal from the menu bar. A text window opens.
In the Terminal window, type this:
resetpassword
That's one word with no spaces. Then press return. A Reset Password window opens. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select  ▹ Restart from the menu bar.

Downloads to documents folder fail due to parallel upload

Hi, mobile documents is a great tool that I use to replicate all business relevant documents to mobile clients. However there is one great disadvantage for me. When you download a file that is a bit larger (>1 MB), during the download the client will already start uploading the temporary file. So the download then fails as it cannot convert the temporary file into the final one.
This is something that does not happen for equivalent clients (for example skydrive). Do you think this is something that can be fixed?
thanks,
Heiko

Hi Heiko,
Let me explain again:
You said "uploader locks the file so that it can no longer be changed". For the temporary file it is the downloader which have locked the file. Hence, the impression that file is getting uploaded because it is locked is hence not correct.
The next version might be available in Q1\Q2 2014. We will keep everyone updated via community.
Best Regards,
Ashwani Kr Sharma

How do I use the Japanese fonts in Font Book in a Pages document?

How does one use the Japanese fonts in Font Book in a Pages document. Pages has its own fonts but I cannot get the Japanese fonts into it.

To type japanese on a computer you change the keyboard, not the font. Go to system prefs/keyboard/input sources and add Japanese/Kotoeri to the list, then select Hiragana in the "flag" menu at the top right of the screen, then type. The font will take care of itself.
http://redcocoon.org/cab/mysoft.html
If you have any further questions, just ask.

7515 ios 8 scanning doesn't function using document feeder

My AiO remote updated on my iPad today and i have issues scanning from the scanner. The printer and tablet functions properly when scanning using the glass however when using the document feeder, AiO remote scans the sheets then before saving it says there is a problem with the scanner, check the scanner. not sure why it works with the glass and NOT with the feeder.

I am having the exact same problem. I will add that scanning from the document feeder to my Mac Book works fine. The problem with the document feeder is only whenn atttempting to use the AiO software on my iPad.

I need to convert PDF file to Word Document, so it can be edited. But the recognizing text options do not have the language that I need. How I can convert the file in the desired of me language?

I need to convert PDF file to Word Document, so it can be edited. But the recognizing text options do not have the language that I need. How I can convert the file in the desired of me language?

The application Acrobat provides no language translation capability.
If you localize the language for OS, MS Office applications, Acrobat, etc to the desired language try again.
Alternative: transfer a copy of content into a web based translation service (Bing or Google provides a free service).
Transfer the output into a word processing program that is localized to the appropriate language.
Do cleanup.
Be well...

BW configuaration documents

Similar Messages

Maybe you are looking for