Landscape of BI and ECC

Hi Folks,
can u tell me the landscape of BI and ECC.
DEV> QTY> PROD in BI
DEV> QTY> PROD in ECC
This is the Landscape, my doubt is from where the Data is passing from ECC to BI (like PROD ECC to PROD BI).
Can u please help me out in this.
Thanks In Advance
Regards,
Naresh.

Hi,
We develop the objects in development server of BI and move to quality for testing.Most of the companies maintain data in quality server which is quite similar to PRD.
Some companies have One server for DEV and QAT ,you can call it a client copy.So whenver you develop new objects or reports you do not need to transfer it from DEV to QAt for testing.
Best practice for transportation is first transport the objects dveloped in R/3 from DEv to QAT and then replicate to BI ,once it is done then transport the BI Objects from DEV to QAT and same procedure for PRD.
Hope it clears your queries.If you need any mnore inputs please let me know.
Regards,
AL

Similar Messages

Can SAP ECC6.0 SR2 and ECC 6.0 SR3 exist on the same landscape.

Dear Tech Masters.
I have done Heterogenous System Copy in Dev and QAS box in Landscape.
Source machine : ECC 6.0 SR2 on Windows 32bit. Oracle 32bit
Target System : ECC 6.0 SR 3 on Windows 64bit, Oracle 64bit.
Now I am going for production installation,
I got stuck with installation in production as I have source for ECC 6.0 SR2 for windows x64 only where as I have done system copy for DEV and QAS using ECC 6.0 SR3 media, though the source instances for Dev, Qas were ECC6.0 SR2.
Please suggest whether its possible to design the landscape with mix of ECC 6.0 SR2 , SR3. Please help asap.

Thanks a lot Vladimir, I am confident now ( technically ) to go ahead with SR2 installation in production.
In production, Should I make it up to the SP level with respect to QAS instance. ( QAS is ECC 6.0 SR3 -system copy ).
One more thing, If SAP will check our landscape, if they found it in this way..will that make any impact in SAP support in future.
Please suggest.
Rabi.
Edited by: RABI PAL on Jan 2, 2009 8:39 AM

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

NW04s BI SPS 20 and ECC 6.0 SPS 16 - SP Update question

Hi SDN,
We are planning for SP update project. Our current landscape is NW04s BI SPS13 (BI ABAP), NW04s Portal SPS13 (BI Java), and ECC SPS 11. All the common components like SAP_BASIS (SP13), SAP_BW(SP15), SAP_ABA(SP13) are in same SP level in all the systems.
Now when we checked with latest SAP stack releases for SAP NW04s(SPS20) and SAP ECC 6.0(SPS18). The SAP_ABA is on SP18 in ECC while in NW04s (ABAP), it is on SP20. Similarly for SAP_Basis, for ECC it is SP18 while NW04s has SP20. More importantly SAP_BW, ECC has SP20 while NetWeaver has SP22.
Can someone please adivice if we can keep SAP_ABA, SAP_Basis and SAP_BW be on different SPs in ECC and BI or do we need to update only these components to same SP as in BI (NW04s SPS20).
Thanks,
Vamshi

Hi Vamshi,
Just update the components to same SP as in BI (NW04s SPS20), Because time and cost matters.
Regards,
Marasa.

BW Landscape Question - DEV and QAS in same Environment

Hi,
I do have a doubt about the following Landscape of my client:
ECC - PRD CLNT 100 --> BW Prod
ECC- DEV CLNT 400 --> BW Dev
ECC- DEV CLNT 100
Basically
ECC- DEV CLNT 400 has MasterData but NO customizing !!
ECC- DEV CLNT 100 has NO MasterData but Cusomtizing !
First I pointed the Source System to DEV CLNT 100 but as has no MData that though was no point on having such connection.
So created the landscape as above described.
The only draw back I can see is that every time I activate some BI_CONT in BWD it replicates it in DEV CLNT 400 for which the client is not open for customization so get the message "no authorization for..."
So the procedure is to activate the Datasources (in ECC) on CLNT 100 where is open for Custo and is automatically visible on CLNT 400.
Think the landscape described above is a proper one or can see any pitfall ?
thank you,
AM

Hi Alex
Regarding your question, there is no right or wrong approach, but one has to understand the purpose of the multiple clients on a system, plan accordingly and depending on the business requirements this drives the landscape.
On a development system, you can have multiple clients for various purposes and have the BW system linked to the relevant client:
- Customizing
- Testing (prefered BW Development connection to an ERP Development system)
- Play
In response to your question, it is a good approach to following and the only pitfall would be someone trying to do transactions in the customizing client and the BW system not been able to extract the data for testing purposes.
Currently I have my BW Development system pointing a ERP Development system which contains 3 clients:
- 1 Client (i.e. 200) for Customizing (customizing only, no transaction data).
- 1 Client (i.e. 220) for Play (copy from the ERP production system which contains master and transaction data).
- 1 Client (i.e. 230) for Testing (copy from the ERP production system which contains master and transaction data).
For the testing and play clients, we can also refresh the data if required, generally we try to do this ever 3 months or when there is a large project to be done, i.e. fiscal year change).
Of these 3 clients, my BW Development system only points to the ERP System's Testing client (client 230) so that the we can test extractions on master and transaction data. All developments done in the ERP Development system for BW is done in the customizing client (client 200), since most of the development work is client independent regarding the extractors, so it would then be automatically in the testing client. We have been using this approach for the last 5 years, with no major issues.
PS: The only issue you may have is regarding the extractors that use classification (transaction CTBW) as there is a client specific issue refer to OSS Note: 588184.
Regards
Derek

How to install both solution manager and ECC Development on same server

Hi All,
Can anyone help me how to install Solution Manager and ECC Development on same server and also whether SLD is required? if yes, then how to setup.
Pls let me know.
Regards,
Karthik

Hi Karthik,
I try to answer you message, my answer may not be sufficient for you.
Install SAP Solution Manager and ECC development as separate systems sharing the same server. So each system will get it's own system id and installation number.
Verify sizing of both systems.
SLD is not mandatory for a SAP Solution Manager. If a SLD already exist in your System Landscape, you can connect SMSY (System Landscape) in transaction SMSY_SETUP with a SLD. Information on System will then be retrieved from SLD, rather via an RFC.
Best regards,
Ruediger Stoecker

How to install both solution manager and ECC Development

Hi All,
Can anyone help me how to install Solution Manager and ECC Development on same server and also whether SLD is required? if yes, then how to setup.
Pls let me know.
Regards,
Karthik

Hi Karthik,
I try to answer you message, my answer may not be sufficient for you.
Install SAP Solution Manager and ECC development as separate systems sharing the same server. So each system will get it's own system id and installation number.
Verify sizing of both systems.
SLD is not mandatory for a SAP Solution Manager. If a SLD already exist in your System Landscape, you can connect SMSY (System Landscape) in transaction SMSY_SETUP with a SLD. Information on System will then be retrieved from SLD, rather via an RFC.
Best regards,
Ruediger Stoecker

RFC connection error between BW 3.5 and ECC 6.0

Hi gurus,
We've defined an RFC destination between BW 3.5 and ECC 6.0. Connection test (SM59) is ok, but authorization one fails and ALEREMOTE users block. These users on both systems have good profiles. We look ST22 and find a runtime error on CALL_FUNCTION_REMOTE_ERROR. We've cleaned source system on BW and RFC destination and we've created one more time, but error doesn't disappear. We've looked OSS but don't find anything.
Any idea? Is there any other place (users, RFC) where we have to change user password on system?
Thanks a lot!
Regards,
Iván.
Edited by: Iván Cabezas Castillo on Nov 6, 2009 12:09 PM

Solved!
This is because of the incompatibility of password handling between
640 and 700 systems.
We have to use a maximum 8 character long password with only capital letters (numbers are also allowed) for the user "ALEREMOTE".
1. Change the password for the user in SAP R/3.
2. Maintain the password in SAP BW for the RFC destination (transaction SM59 - Logon/Security tab)
3. Authorization test is now successful.
(SM59 - Test - Authorization).
Regards!

SSO issue with BI 4.0 BW and ECC

We currently have SAP BW 7.3 BOBJ 4.0 ECC and SAP portals.
We have configured SAP BW, BOBJ and SAP Portal with SSO and that works perfectly fine.
The issue is that i have Crystal Reports running on ECC that have also to be published to the Portal.
All BW crystal reports run fine and ECC fails because of SSO -
What am i missing here -
Do i need to do something different for ECC
In CMC Authentication i have added SAP ECC and imported a role - So now i have 2 ids - one from BW and the other from ECC.
I know this is not the way to do it but it still does not work.
What do i need to do to have ECC and BW reports to work with SSO from SAP portal.
Thanks

Thank you for your reply Ingo
I assume that your BusinessObjects Server has the SAP Authentication for BW and ECC configured ?
*Yes *
Are the reports for BW and ECC been called from the portal ?
Yes
if so then you have one BOE Server, 2 SAP environments and 2 SAP authentications configured and to achieve SSO for all systems you will have to combine the 2 SAP Systems via SNC (for XI 3.1) or via the SSO Token Service in BI4
We are on BI4 and we have set up SSO Token for BW -
Are you saying that we have to set up SSO token for BW as well as ECC -
In CMC - Authentication - SAP - Options -SAP SSO Service - it does not give me an option to have 2 systems
How do i add ECC system there too.
Regards
Ryan

Is there any difference between R/3 4.7 version and ECC 5.0????

Hi All,
Is there any difference between R/3 4.7 version and ECC 5.0 for the transaction RSA5.
Regards,
Andy

Andy
Functionality wise I didn't see any difference other than new datasources in ECC5.0
Thnaks
Sat

What is the difference between ECC 5 and ECC 6.0

Dear Experts,
Can any one tell me in detail the difference between SAP R/3 versions ECC 5 and ECC 6 functionality wise in MM mdoule?
To be specific what are the new features in MM being added in ECC 6.0 when compared with ECC 5.
Request your help in this regard.
Rgds,
Uzair
Edited by: Mohd Uzair Hussain on Jul 23, 2008 5:35 PM

Hi,
Refer following link;
[SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
- Goods receipt
- Goods issue
- Transfer posting
- Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
- To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
- Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
- Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
- Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
- 107: Goods receipt to valuated goods receipt blocked stock
- 109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location

SNP planned order availability date difference between APO and ECC

Hi,
I have observed that SNP Planned order availability date is not matching between APO and ECC. Details are as follows.
I ran SNP Optimizer with bucket offset of 0.5. After publishing the optimizer created planned orders to ECC, only start date is matching.
Example:
I am using PDS as a source of supply.
Fixed production activity in SNP PDS is 1 day.
GR processing time: 3 day
After running optimizer planned order is created with dates explained below.
Start date/time: 09.05.2011 00:00:00
End date/time: 12.05.2011 23:59:59
Availability date: 16.05.2011 00:00:00
Because of bucket offset defined as 0.5 optimizer planned order availability is start of next monday.
After publishing this planned order to ECC dates on the planned order is as follows.
Start date: 09.05.2011
End date: 09.05.2011
Availability date: 12.05.2011
I have not maintained any scheduling margin key in ECC. Also if I dont define the GR processing time, planned dates between APO and ECC always match. Can anyone explain the impact of GR time on the availability date.
Regards,
Venkat

Hi Venkadesh,
What's "state stamp"? Do you mean different time zone?
note : 645597 mentioned by Nandha is very helpful:
In standard, CCR will use duedate - "the available date of the output product".
Nandha's words "In SAP APO, if the receipt date of the primary product deviates from the
end date of the last activity of the order, the receipt date
always identifies this as inconsistent. You cannot rectify
inconsistencies of this type by using CCR."
I guess in your PDS or PPM, the output product is not assigned to the End of the last activity. Someone changed it?
Please CIF the PDS or PPM again.
If you really want to apply a note, please use note 815509 as you're using planned order,
and system will use order end date in CCR instead.
GR time is always considered. BR/Tiemin

What are the difference in transaction codes in 4.6 C and ECC 6.0 HCM syste

Hi
What are the difference in transaction codes in 4.6 C and ECC 6.0 in HCM SAP.
Regards,
Sanjay

Believe there will not be any change in Tcodes.
check these links
http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes
http://service.sap.com/upgrade for functional
https://websmp105.sap-ag.de/upgrade

SAP Data Archiving in R/3 4.6C and ECC 6.0.

Hi Guys,
Need some suggestions,
We currently working on SAP R/3 4.6 and have plans to upgrade it to ECC 6.0,
In the mean time there is an requirement for SAP Data Archiving for reducing the database size and increase system performance.So wanted to know if its better to do Data Archiving before upgrade or after. Technically which will be comfortable, Also wanted to know if any advanced method available in ECC 6.0 compared to SAP R/3 4.6.
Please provide your valuable suggestion.
Thanks and Regards
Deepu

Hi Deepu,
With respect to archiving process there will be no major difference in 4.6 and ECC 6.0 system. However you may get more advantage in ECC6.0 system because of Archive routing and also upgraded Write, Delete programs (upgraded program will depend on your current program in 4.6 system). For example In 4.6 system for archive MM_EKKO write program RM06EW30, archiving of purchase document is based on company code in the selection criteria and there is no preprocessing functionality. In ECC 6.0 you can archive by purchase organization selection criteria and preprocessing functionality will additional help in archiving of PO.
In case if you archive documents in 4.6 and later upgrade it to ECC 6.0, SAP system will assure you to retrieve the archived data.
With this i can say that going with archiving after upgrade to ECC 6.0 system will be better with respect to archiving process.
-Thanks,
Ajay

SAP R/3 4.7 and ECC 5.0

Hello MM gurus!
i would like to know differences between SAP r/3 4.7 and ECC 5.0, and what makes the client to opt of the 4.7 or ECC 5.0.
Thanks in Advance gurus.
Regards,
Pieadad.

I am sorry for posting the question without searching properly. i got the answer for my question.
Regards,
Pieadad.

Landscape of BI and ECC

Similar Messages

Maybe you are looking for