Asset Scenario for R/3 4.6 and ECC 6

Hi Everyone,
My client was using all Asset Transaction in SAP 4.6 version like Asset purchase, Depn. Calculation, Retirement and other upto 2004. After that they haven't use the asset transaction....
Now they want to use all the asset transaction in SAP ECC6. But, the asset master which they had used in SAP 4.6, has moved to ECC 6 and they would like to add new asset list which had purchased after 2004.
Now i want to know, how to treat the Previous Asset and New Asset list in Ecc 6....
Is there any configuration wise we have to change?
Thanks and Regards,
M.Mohan.
Edited by: Mohan on Feb 1, 2010 2:01 PM

The only change is The depreciation run (numberange from the FI document is internal, the depreciation run post only online)
New transaction with depreciation log
periodical postings post only online.
In config there are some changes.
Only when you are activate EA-FIN there are functional changes

Similar Messages

Transaction type to dispose the asset only for the depn areas 01 and 02

One of the Company codes XXXX plant XXXX has an isuue for asset # XXXXXXXXXX-0 this asset was partially retired in Nov.2008 and now its acquisition value is JPY312,428
which should not be an asset under US GAAP but qualify for asset under Tax book . So it needs be removed from US and JCC book(01 and 02 area) but keep the record on the Tax book(area 15).
Is there any transaction type to dispose this asset only for the 01 and 02 area but keep the historical data for 15 area?
Thanks for helping in advance

Can I suggest you a way to handle this? Just give a try and see whether it works for you or not.
Post a Credit entry to the Asset only to the area 01 and 02. Please follow the below steps before you do this.
1. Go to main SAP screen => System => User profile => Own data => Parameters
Add parameter ID FAA_FB01_AREA_SWITCH (Turn On Value Entry at Area Level for FB01) and mark "x" against it in Parameter value. Save this changes.
2. Go to F-02, Enter the Asset number (posting key 75 and transaction type 105, which ever you feel like) and then in the next screen, enter the amount. Here in this screen, you will find a tab named area values. Click that tab and change the values Area 01 & 02 to $0.01 and leave the Area 15 as it is. Enter the appropriate dr line item and save the document.
3.Go to AW01N and see tha values against each of the areas.
please revert in case you have any questions.

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

Query for SAP NW 7.0 and ECC

Dear ALL ,
We have purchased SAP NW 7.0 License .We have installed it with 2 components WAS ABAP and WAS as JAVA.
Now my question is: this SAP NW 7.0 installation does not contain any functional module like SAP HR.MM,FI etc...
for this requirement do we need to take a separate license of SAP ECC or do we need to install some contentson this SAP NW 7.0 server so that we can run functional code on this server????
Please suggest....
Thanks
sandeep

Hi Sandeep.
The problem is not only the license, but also the application itself. If you have installed NW, your system don't have the tables and programs needed to execute business modules like FI, SD, MM, etc.
If you need those modules, you have to install an ERP 6.0 from scratch.
Regards
Francisco

Difference in workflow tables for the versions 4.6C and ECC

Hello,
Could someone please let me know as to what changes have been made by SAP in the workflow tables from 4.6c to ECC version?
Thanks,
Samson

Hi
Check these Tables
SWW_OUTBOX - Lists Workflows in outbox together with status
SWW_CONT - Container Contents for Work Item Data Container
SWW_CONTOB - Container Cont. for Work Item Data Container (Only Objects)
SWWLOGHIST - History of a work item
SWWORGTASK - Assignment of WIs to Org.Units and Tasks
SWWUSERWI - Current Work Items Assigned to a User
SWWWIHEAD - Header Table for all Work Item Types
SWW_WI2OBJ - Workflow Runtime: Relation of Work Item to Object
Regards,
Surjith

ALE for communicating SAP 4.7 and ECC 6.0

Dear All,
Plz guide me to create RFC,PORT,Distribute Model as I want to transfer data from SAP 4.7 to ECC 6.
thanks,
RP

i defined port and rfc tested its working.
BUT WHEN I DEFINE MODEL VIEW IT ASK FOR LOGICAL SYSTEM FOR DESTINATION.
HERE MY SOURCE : SAP 4.7
DESTINATION : ECC 6.0
NOW TELL ME WHAT TO DO
Plz help me
RP

Workflow scenarios for FS-CD module

Hi All
I am working for FS-CD module for workflow and I am working on FPY1 transaction code for triggering some workitems based on the clients requirements. Could anyone provide me some workflow scenarios for the above said transaction and also for the FS-CD module.
Thanks
Ashok

Hi Ashok,
Please go to transaction code SWDM to find all the standard SAP workflows for any application component.
There you can specify the module as FS-CD.
Thanks & Regards,
Deb

Scenarios for routines

Hi,
can any one send scenarios for writing routines in TR and in UR amd xplain of hoe to write the routines.
points will be rewarded for your replies.

Hi,
Start Routine
Start routines are executed prior to applying the other transfer rules. They have access
to all the records in the data package (not the extracted data set!). The most practical
use of start routines is to preload tables into memory for efficient nontrivial table
lookups or to apply complex record filters to the data package. However, you must
take care not break the memory limits of the application server, especially having in
mind that multiple data packages executed at the same time will each require the same
amount of memory.
InfoObject Transfer Routines
InfoObject transfer routines are transfer routines directly tied to an InfoObject. In whatever set of transfer rules this InfoObject is used, the specified routine will be executed.
InfoObject transfer routines are used to warrant consistent systemwide transformations
for a specific InfoObject. They are maintained in the InfoObject maintenance
transaction .
Page 287/288
Source: Mastering the SAP Business InformationWarehouse
Update Rules
Having applied the transformation rules, SAP BW is now ready to apply applicationspecific
transformations in the update rules that are independent of the source system.
The logic behind the update rules is more complex than the one behind the transfer
rules: Data integration transformations are still supported, but the main focus is on
application logic transformations such as normalization, denormalization, and aggregation.
Analogous to the transfer rules, we present a highly simplified update rules
algorithm at the end of this section. To understand the following discussion you just
need to know that the update rules handle key figures (data fields) and characteristics
(key fields) differently when updating InfoCubes (ODS objects, master data tables):
Every characteristic (key field) update rule is executed for each of the key figures (data
fields) of the InfoCube (ODS object, master data table). Each of the key figure (data
field) update rules generates an in-memory result record with all characteristics (key
fields) values and the key figure (data field) value filled.
Start Routine
Start routines, in update rules are essentially the same as in transfer rules.
Page 300
Source: Mastering the SAP Business InformationWarehouse
Refer.
How To Routines within Transformations
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6090a621-c170-2910-c1ab-d9203321ee19
Thanks,
JituK

IDES Bus Scenarios for SAP IS-OIL solutions

Will anyone provide url for Business scenarios for SAP IS-OIL SD and MM modules

Here is the link go through it,
http://help.sap.com/bp_bblibrary/600/HTML/X14_EN_AU.htm
Regards,
Rao

Sample scenarios for proxies

hi
can any one provide me with sample scenarios for
abap proxies ,both inbound and out bound
regards
ram

Hi,
ABAP client proxy
ABAP Proxies in XI(Client Proxy)
ABAP server proxy
ABAP Server Proxies
Proxy generation
http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm
Debug Proxy
XI: Debug your inbound ABAP Proxy implementation
Monitor the processed msgs
Monitoring for Processed XML messages in ABAP Proxy

NW2004s portal password and ECC 6.0 password synchronisation

Hi,
We have implemented NW2004s SR2 SPS 12 portal and also configured SSO
between Netweaver portal and ECC 6.0 system using SAP logon tickets.
As per client's requirement, is there any standard mechanism available
for synchronizing Netweaver portal password and ECC 6.0 system
password? (i.e when we change password in EP the same is reflected in
ECC also).
Appreciate your inputs.
Regards,
Lakshmi.

Hi Lakshmi,
I am not sure of this, but yes one can use central user administration (CUA), for synchronising userid/pwd from a single system.
The CUA box will hold all the user ID.
Regards,
Akshay
Reward if helpful.

LE/WM functionality difference between 4.6c and ECC 6.0

Hi,
     I am looking for functionality differences between 4.6c and ECC 6.0 for LE and WM in particular. I have already checked the sites related to overall differences. I am particularly looking for differences between 4.6c and ECC 6.0 in Warehouse Management and Logistics Execution. Helpful answers will be rewarded.
cheers,
Sarvesh

This is what I have gathered from this thread.
R 4.7 New Functionality in WM:
     Cross Docking
     Value Added Services
     Task and Resource Management
     Dynamic Cycle Counting
     Yard Management
Effect of ECC 5.0 on WM:
Archiving Data has been improved
ECC 6.0 Version comparison link
http://solutionbrowser.erp.sap.fmpmedia.com/
     Picking Consolidation for many deliveries
     RFID integration
     Enhanced Cross Docking
     Enhanced Task and Resource Management

Business scenarios for daily, weekly and nightly loads!!

Can any body tell some Business scenarios for daily, weekly and nightly loads where we monitor the loads in Production support.
Regards
srikanth.ch

Hi,
It all depends on your business needs. In general on daily basis you will load the SD and MM which will cover all the stock and sales done for day. Generally most of the clients use Lo Cockpit extraction for both the modules. FI chains will run on month end for example the AP(Accounts Payable),AR(Accounts Receivable) chains will be run on the month end.
Some SD datasources : 2lis_13_vdhdr, 2lis_13_vditm, 2lis_13_vdkon - all these to pull billing related data
Some MM Datasource : 2lis_03_bx and 2lis_03_bf.
Regards,
Harish Raju

Scenario for interface between a non sap system and a SAP erp

Hello,
I need some help in order to elaborate a interface between a SAP ERP and a non-sap system with the help of a XI system.
   - At first regarding the interface from the non sap system and a SAP ERP :
       the non sap system sends a flat file to the XI system. The flat file contains a row with header data and rows with item data. We were thinking when the file arrives to the XI system, to save the data in a header database and in a items database in XI. is it possible ?
And then to have like a job that reads the database and creates idoc and sends them to the SAP erp and updates the xi header and items database with a flag that means that the records have been sent to the SAP erp.
   -   Regarding the interface SAP erp to non SAP system:
       the SAP erp sends idoc to XI. Then the idocs are transformed into flat file.
Is this scenario possible ?
Do we need any adaptator between the non sap system and the XI ?
Thank you for your help
Christophe

Hi Bontron,
Idoc doesnot support synchronous call. So you can use either proxy or function module and inturn call the idoc from them and send response back to xi. You need to have two scenarios for your design.
Scenario1:   Source File (file adapter) -- xi -- Dump into database tables (Jdbc Adapter)
Scenrio2: Pickup form Database tables (Jdbc Adapter) -- xi -- RFC Adapter ---> This is synchronous call.
Regarding the interface SAP erp to non SAP system
You can send idoc to xi and from there use File adapter to send to the receiving system.
These blogs may help you to some extent:
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
https://wiki.sdn.sap.com/wiki/display/XI/step%2bby%2bstep%2bRFC%2bto%2bJDBC%2bscenario   (your scenario will be opposite to this)
Regards,
---Satish

Documentation on Integration Scenarios for BAS-PV and DES

Hi,
Is there any documentation on the Integration Scenarios for BAS Postal Validation, and Duplicate-Check and Error-Tolerant Search for ECC 5.0?
What we have is only for R3 4.6, and the behavior of business partners for ECC 5.0 is very much different as compared to R3 4.6.
Thanks!

The newest release of the sharepoint kit called internally (ipoint) should work fine with java infoview. I haven't set this up my self and you may need to open an incident with support to verify if Edge supports the newest sharepoint kit.
Regards,
Tim

Asset Scenario for R/3 4.6 and ECC 6

Similar Messages

Maybe you are looking for