SAP Latest ,plz refer

We are for looking for
SAP IS Retail experts for Mumbai
SAP APO or SCM with demand planning, PPDS, SNP modules exposure for Calcutta, Mumbai, Bangalore.
Relevant exp : 4 – 5yrs
Salary : no constraint
Position : 4 slots in each.
3) Job Title: SAP Consultant
Design, develop, test and support RFC and BAPI programs for EASY create, change and display of SAP Standard transactions, Front Office processes, custom programs and Custom workflows using ABAP/4 in an architecture comprising of SAP R/3, BEA Web logic portal platform and Web methods EAI. Also Design, develop, test and support ABAP programs in user exits, custom programs and workflows.
Required:
·         Extensive experience with RFC and BAPI programming
Experience with SAP function modules, function groups, and module pools
Experience in data republication between Web logic portal and R/3 system
Experience with Call transacti! ons, User Exits and BADI’s
Experience with Dialog programming and Interface programming
Experience with SAP Script and Smart Forms
Experience with Web Methods EAI Adaptors
Experience with Data Dictionary, ABAP workbench, Report programming, Workflow programming, ABAP Objects, BDC, ALE and IDOC
Experience to develop detailed technical design documents based on requirements
Experience to develop and support RFC and BAPI programs within SAP R/3, BEA Web Logic Server portal and Web methods EAI environment
A self motivated individual with strong communication skills
To work as a team player, to follow the defined work process and to produce documentation deliverables as required f! or a validated system
Highly Desired:
SAP CCS master data objects, tables, function modules etc.
Experience with CIC0
Good working knowledge, problem solving and techno-functional skills related to one or more functional areas of CCS such as; Customer Service, Work management, Device management, Billing & Invoicing and FI-CA
Technical design and programming creativity in coming up with a master architecture within SAP R/3, BEA Web logic portal platform and Web methods EAI
Print workbench tool, Regular and collective invoice application forms
Essentials
5+ Years Hands on Experience in SAP ABAP/4
Regards
Srinivas
09902039398
[email protected]

Its a shame that you have decided to post a job requirement here. In my opinion you should be barred from using this portal.
You, and people like should leave this alone for the developers who are trying to help each other by sharing their knowledge.
I will also report you to SDN admin.
Biren Bugati

Similar Messages

  • Sap plz refe

    Hi
    Greetings to you all.
    We are looking for:
    SAP IS Retail experts for Mumbai
    SAP APO or SCM with demand planning, PPDS, SNP modules exposure for Calcutta, Mumbai, Bangalore.
    SAP CCS - Bangalore
    Relevant exp : 4 – 5yrs
    Salary : no constraint
    Can anyone refere some SAP Professionals please.
    we also have some other SAP openings for all modules.
    Regards
    Srinivas
    9902039398
    [email protected]

    hi srinivas,
    these are the some reference no for sap openings,
    sap-bw - suresh babu - 9901696477,
    sap-fice - ramesb -9980906813

  • SAp plz refer

    Hi
    Greetings to you all.
    We are looking for:
    SAP IS Retail experts for Mumbai
    SAP APO or SCM with demand planning, PPDS, SNP modules exposure for Calcutta, Mumbai, Bangalore.
    SAP CCS - Bangalore
    Relevant exp : 4 – 5yrs
    Salary : no constraint
    Can anyone refere some SAP Professionals please.
    we also have some other SAP openings for all modules.
    Regards
    Srinivas
    9902039398
    [email protected]

    hi srinivas,
    these are the some reference no for sap openings,
    sap-bw - suresh babu - 9901696477,
    sap-fice - ramesb -9980906813

  • HI I am attending an interview in tcs in sap abap plz send me interivew que

    Hi I am attending tcs interivew this week plz send me interivew questions wht they ask ,,,my id is [email protected] ,,,, than k u,,,

    Hi,,
    Please find a few collection of my interview ques..
    Mark if useful..
    1. How data is stored in cluster table?
    Each field of cluster table behaves as tables which contains the no. of entries.
    2. What are client dependant objects in abap/sap?
    SAP Script layout, text element, and some DDIC objects.
    3. On which even we can validate the input fields in module progams?
    In PAI (Write field statement on field you want to validate, if you want to validate group of fields put in chain and End chain statement.)
    4. In selection screen I have three fields, plant mat no and material group. If I input plant how do I get the mat no and material group based on plant dynamically?
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR MATERIAL.
    CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST' to get material and material group for the plant.
    5. How do you get output from IDOC?
    Data in IDOc is stored in segments, the output from Idoc is obtained by reading the data stored in its respective segments.
    6. When top of the page event is triggered?
    After excuteing first write statement in start-of-selection event.
    7. Can we create field without data element and how?
    In SE11 one option is available above the fields strip. Data element/ direct type.
    8. How do we debug sapscript?
    Go to SE71 give lay set name , go to utilities select debugger mode on.                              
    9. Which transaction code can I used to analyze the performance of ABAP program.                              
    TCode AL21.                              
    10. How can I copy a standard table to make my own z_table.                              
    Go to transaction SE11. Then there is one option to copy table. Press that button. Enter the name of the standard table and in the Target table enter Z table name and press enter.                              
    Following are some of the answers which I gave upto my knowledge.                              
    1. What is the use of 'outerjoin'                              
    Ans. With the use of outer join you can join the tables even there is no entry in all the tables used in the view.                              
    In case of inner join there should be an entry in al the tables use in the view.                              
    2. When to use logical database?                              
    Ans. Advantage of Logical databases:                              
    less coding s required to retrieve data compared to normal internel tables.                              
    Tables used LDB are in hierarchial structure.                              
    3. What is the use of 'table index'?
    Ans .Index is used for faster access of data base tables.
    4. What is the use of 'FOR ALL ENTRIES'?
    Ans. To avoid nested select statements we use SELECT FOR ALL ENTRIES statement.
    If there r more than 10000 records SELECT FOR ALL ENTRIES is used.
    Performance wise SELECT FOR ALL ENTRIES is better to use.
    5. Can you set up background processing using CALL TRANSACTION?
    Yes,Using No Screen Mode.
    6. What are table buffers?
    Table buffers reside locally on each application server in the system. The data of buffered tables can thus be accessed
    directly from the buffer of the application server. This avoids the time-consuming process of accessing the database.
    Buffering is useful if table needs to be accessed more no. of times in a program.
    ABAP Technical Interview Questions:               
    1. What is the typical structure of an ABAP program?               
    2. What are field symbols and field groups.? Have you used "component idx of structure" clause with field groups?               
    3. What should be the approach for writing a BDC program?               
    4. What is a batch input session?               
    5. What is the alternative to batch input session?               
    6. A situation: An ABAP program creates a batch input session. We need to submit the program and the batch session in background. How to do it?               
    7. What is the difference between a pool table and a transparent table and how they are stored at the database level?               
    8. What are the problems in processing batch input sessions? How is batch input process different from processing on line?               
    9. What do you define in the domain and data element?               
    10. What are the different types of data dictionary objects?               
    11. How many types of tables exist and what are they in data dictionary?               
    12. What is the step-by-step process to create a table in data dictionary?
    13. Can a transparent table exist in data dictionary but not in the database physically?
    14. What are the domains and data elements?
    15. Can you create a table with fields not referring to data elements?
    16. What is the advantage of structures? How do you use them in the ABAP programs?
    17. What does an extract statement do in the ABAP program?
    18. What is a collect statement? How is it different from append?
    19. What is open sql vs native sql?
    20. What does an EXEC SQL stmt do in ABAP? What is the disadvantage of using it?
    21. What is the meaning of ABAP editor integrated with ABAP data dictionary?
    22. What are the events in ABAP language?
    23. What is an interactive report? What is the obvious diff of such report compared with classical type reports?
    24. What is a drill down report?
    25. How do you write a function module in SAP? Describe.
    26. What are the exceptions in function module?
    27. What is a function group?
    28. How are the date abd time field values stored in SAP?
    29. What are the fields in a BDC_Tab Table?
    30. Name a few data dictionary objects?
    31. What happens when a table is activated in DD?
    32. What is a check table and what is a value table?
    33. What are match codes? Describe?
    34. What transactions do you use for data analysis?
    35. What is table maintenance generator?
    36. What are ranges? What are number ranges?
    37. What are select options and what is the diff from parameters?
    38. How do you validate the selection criteria of a report? And how do you display initial values in a selection screen?
    39. What are selection texts?
    40. What is CTS and what do you know about it?
    41. When a program is created and need to be transported to prodn does selection texts always go with it? if not how do you make sure? Can you change the CTS entries? How do you do it?
    42. What is the client concept in SAP? What is the meaning of client independent?
    43. Are programs client dependent?
    44. Name a few system global variables you can use in ABAP programs?                              
    45. What are internal tables? How do you get the number of lines in an internal table? How to use a specific number occurs statement?                              
    46. How do you take care of performance issues in your ABAP programs?                              
    47. What are datasets?                              
    48. How to find the return code of a stmt in ABAP programs?                              
    49. What are interface/conversion programs in SAP?                              
    50. Have you used SAP supplied programs to load master data?                              
    2. Adapted from response by Maram Roja on Tuesday, June 15, 2004                              
    1. What are the techniques involved in using SAP supplied programs? Do you prefer to write your own programs to load master data? Why?                              
    2. What are logical databases? What are the advantages/disadvantages of logical databases?                              
    3. What specific statements do you using when writing a drill down report?                              
    4. What are different tools to report data in SAP? What all have you used?                              
    5. What are the advantages and disadvantages of ABAP query tool?                              
    6. What are the functional areas? User groups? How does ABAP query work in relation to these?                              
    7. Is a logical database a requirement/must to write an ABAP query?          
    8. What is the structure of a BDC sessions.          
    9. What are Change header/detail tables? Have you used them?          
    10. What do you do when the system crashes in the middle of a BDC batch session?          
    11. What do you do with errors in BDC batch sessions?          
    12. How do you set up background jobs in SAP? What are the steps? What are the event driven batch jobs?          
    13. Is it possible to run host command from SAP environment? How do you run?          
    14. What kind of financial periods exist in SAP? What is the relevant table for that?          
    15. Does SAP handle multiple currencies? Multiple languages?          
    16. What is a currency factoring technique?          
    17. How do you document ABAP programs? Do you use program documentation menu option?          
    18. What is SAPscript and layout set?          
    19. What are the ABAP commands that link to a layout set?          
    20. What is output determination?          
    ABAP Interview Questions          
    1.Without using Tcode SE11, How can we enter the values in to the table???
    2.What is the difference between Collect statement and Append Statement???
    3.What do you mean by correction and Transportation system???
    4.What is the difference between User Exits and BADI????
    5.How can we identify User exits in our screen???
    6.What do you mean by Inbound and Outbound interface???
    7.In realtime do we configure ALE systems or Administator will take care of that??
    8.How to release an object???
    9.What is the flow of a Sales document???
    10.What is the flow of Purchase order???
    12.What is the flow of Invoice???
    13.What are the standard IDOC's used???
    14.What do you mean by table control???Where will we use this???
    15.What are field symbols??Where will we use these symbols???
    Deepti
    1. There are other ways of entering data into a DB table. ex. B D C
    2. Collect statement collect/adds the records basing on a key field. allows to create summarised data sets.
    Append will append/add a record at the end of existing records
    8. to release an object - use se10/se9
    9. sales doc flow: S. A. - S. O. - Delivery - Billing
    12. Delivery - invoice.
    15. field symbols are used for dynamic allocation. at runtime u can assign a concrete field to field-symbol.
    Kishore
    1. you can go to abap editor (se38) and use insert statement for insertion update for update and modify for modifications.
    2. collect will not allow duplicate entries, while append can allow duplicates.
    3. if any changes are made to objects they are to be transported to different systems i.e, change and transport.
    4. in user exits we go by general method for enhancements while BADIs we use objects (oops concepts)
    methods for enhancement.
    14. table controls are enhanced version for step loops where we can expand rows .main difference between these two
    is step loop can be expanded to two lines table controls can`t.
    15. field symbols are just like pointers concept which are used in C language. We use them when we want to refer to
    the fields considered,it doesnt allocate any memory for it.
    Venu Rapolu     
    1. Ans: Using BDC., LSMW,,ALE., BAPI     
    2. Ans: Collect: it adds the numeric fields to the existing non numeric key field records., thereby avoiding duplicate     
    values., and append will simply adds the record     
    3 . Ans: The CTS contains work bench organizer and transport system :     
    The workbench organizer is used to record and contol changes to the ABAP/4 development objects;     
    The transport system is used to move objects from an SAP dev.system to production system     
    6. Ans: Outbound interface is used to send IDocs to the ALE server.,     
    Inbound interface is used to Analyse the received Idoc.     
    7. Ans: We (ABAPers) don't do.     
    8. Ans: se09 or se10     
    13. Ans: MATMAS     
    CREMAS     
    DEBMAS     
    GLMAST etc...     
    14. Ans: to display records in table format., we use in Screens     
    15. Ans: we assign the field content at run time with ASSIGN stmt.
    Satish D
    1. goto se16 u can view the table contents
    2. collect will collects all the numeric fields of nonnumeric field values
    append will append record at the end of table
    3. when we are creatiing new task like dev. a new prg.. after completion of dev. that will be trnsported to testing system or production system to do that we are assigning an
    transport request from our dev.class(system) by using se09
    4. badis are dev. by class and inheritence methods where as user exitsdev by SAP only and empty shells filled wit user logic
    5. go to system then status
    6. outbound generating an idoc in ale layer with master_idoc_create_messgetype,
    inbound is receivng system with idoc_inbound_process, gives an return variable wether it is sucess or not
    7. no we have to configur that
    8. go to se09 or se01 there write your task no and use release button it will asks whats the other system name
    and number enter them and relase by pressing jeep button
    9. inquiry
    quotation
    sales order                    
    shipping                    
    delivery                    
    invoice                    
    return goods                    
    12. after creation of delivry note invoice is prepared                    
    13. master_idoc_distribute will generate standard idoc                    
    Deepti                    
    I am enclosing some of answers which I know.                    
    1. We can use t.Code SE16 to enter values into table only if table maintainence is allowed for that table.                    
    2. Append will add new entries into the table where as collect add into the numeric type fields if other charatcer fields                    
    matches to your selection criteria.                    
    3. CTS used for creation of ABAP development transport requests.The transaction code for this is SE10.                    
    4. UserExits r used for adding additional functionality to the existing SAP standard transactions.Using UserExits we can add additional functionality standard SAP functionality without making any changes to the original code.BADI is a standardized interface for ABAP sources that enables partners and customers to enhance SAP-delivered programs in their namespace.                    
    5 .We can identify User exits by using transactions CMOD and SMOD.               
    6. After entering transaction code SE10 select the transport request which u want to transport and click on transport icon(Truck symbol) to release it.               
    10. Purchase Requistion->RFQ->Vendor Evaluation->Purchase Order(ME21).               
    14. Table control is the only facility provide thru dialog programming when we come acrosse the use of updating standared,deletion,insertion and all database operations.               
    15. Field symbols r pointers to the existing data types(like 'C') which does not allocate any memory space. These are used faster access of data.               
    Answers to some ABAP Interview Questions:               
    Questions which I have faced in an interview:               
    1) What is runtime analysis? Have you used this?               
    2) What is meant by performance analysis? Have done anything to improve the performance?               
    3) How to transfer the objects? Have to transferred any objects?               
    4) How did you test the developed objects?               
    5) What is the difference between SAP Memory and ABAP Memory?               
    6) In order to upload Purchase order details, how you handle multiple values for a single field?               
    Eg: Item field may contain no. of values for a record               
    7) What is the procedure you followed to upload the data?               
    8) How did you handle errors in Call Transaction?
    9) Among the Call Transaction and Session Method, which is faster?
    10) What are the difference between Interactive and Drill Down Reports?
    11) How to pass the variables to forms?
    12) How to create a link between modified form and modified print program?
    13) What is the table, which contain the details of all the name of the programs and forms?
    14) How did you test the form u developed? How did you taken print?
    15) What are Standard Texts?
    16) What is the difference between Clustered Tables and Pooled Tables?
    17) What is pf-status?
    18) Among "Move" and "Move Corresponding", which is efficient one?
    19) What are the output type and Tcodes?
    20) Where we use Chain and Endchain?
    21) Do you use select statement in loop endloop, how will be the performance? To improve the performance?
    22) In select-options, how to get the default values as current month first date and last date by default?
    Eg: 1/12/2004 and 31/12/2004
    Go thru these answers:          
    1) What is runtime analysis? Have you used this?          
    It's checks program execution time in microseconds. When you go to se30.if you give desired program name in performance file. It will take you to below screen. You can get how much past is your program.          
    2) What is meant by performance analysis? Have done          
    3) How to transfer the objects? Have you transferred any objects?          
    4) How did you test the developed objects?          
    I was testing a developed object. There are two types of testing          
    - Negative testing          
    - Positive testing          
    In negative testing we will give negative data in input and we check any errors occurs.          
    In positive testing we will give positive data in input for checking errors.          
    8) How did you handle errors in Call Transaction?
    We can create a internal table like 'bsgmcgcoll'. All the messages will go to internal table. We can get errors in this internal table.
    Below messages are go to internal table. when you run the call transaction.
    - Message type
    - Message id
    - Message Number
    - Variable1
    - Variable2
    - Variable3
    9) Among the Call Transaction and Session Method, which is faster?
    Call transaction is faster then session method. But usually we use session method in real time...because we can transfer large amount of data from internal table to database and if any errors in a session. Process will not complete until session get correct.
    10) What are the difference between Interactive and Drill Down Reports?
    ABAP/4 provides some interactive events on lists such as AT LINE-SELECTION (double click) or AT USER-COMMAND (pressing a button). You can use these events to move through layers of information about individual items in a list.
    Drill down report is nothing but interactive report...drilldown means above paragraph only.
    11) How to pass the variables to forms?
    12) What is the table, which contain the details of all the name of the programs and forms?
    Table contains vertical and horizontal lines. We can store the data in table as blocks. We can scroll depends upon your wish. And these all are stored in database (data dictionary).
    Which contain the details of all the name of the programs and forms? (I don't know).
    13) How did you test the form u developed? How did you taken print?
    14) What are Standard Texts?
    16) What is the difference between Clustered Tables and Pooled Tables?
    A pooled table is used to combine several logical tables in the ABAP/4 dictionary. Pooled tables are logical tables that must be assigned to a table pool when they are defined.
    Cluster table are logical tables that must be assigned to a table cluster when they are defined.
    Cluster table can be used to store control data they can also used to store temporary data or text such as documentation.
    17) What is pf-status?
    Pf status is used in interactive report for enhancing the functionality. If we go to se41, we can get menus, items and different function keys, which we are using for secondary list in interactive report.
    18) Among "Move" and "Move Corresponding", which is efficient one?
    I guess, 'move corresponding' is very efficient then 'move' statement. Because usually we use this stamtent for internal table fields only...so if we give move corresponding. Those fields only moving to other place (what ever you want).
    19) What are the output type and Tcodes?
    20) Where we use Chain and End chain?
    21) Do you use select statement in loop end loop, how will be the performance? To improve the performance?                    
    22) In select-options, how to get the default values as current month first date and last date by default?                    
    Eg: 1/12/2004 and 31/12/2004                    
    SAP ABAP interview questions                    
    Thanks to the reader who sent in this question set:                    
    1. What is an ABAP data dictionary?- ABAP 4 data dictionary describes the logical structures of the objects used in application development and shows how they are mapped to the underlying relational database in tables/views.                    
    2. What are domains and data element?- Domains:Domain is the central object for describing the technical characteristics of an attribute of an business objects. It describes the value range of the field. Data Element: It is used to describe the semantic definition of the table fields like description the field. Data element describes how a field can be displayed to end-user.                    
    3. What is foreign key relationship?- A relationship which can be defined between tables and must be explicitly defined at field level. Foreign keys are used to ensure the consistency of data. Data entered should be checked against existing data to ensure that there are now contradiction. While defining foreign key relationship cardinality has to be specified. Cardinality mentions how many dependent records or how referenced records are possible.                    
    4. Describe data classes.- Master data: It is the data which is seldomly changed. Transaction data: It is the data which is often changed. Organization data: It is a customizing data which is entered in the system when the system is configured and is then rarely changed. System data:It is the data which R/3 system needs for itself.                    
    5. What are indexes?- Indexes are described as a copy of a database table reduced to specific fields. This data exists in sorted form. This sorting form ease fast access to the field of the tables. In order that other fields are also read, a pointer to the associated record of the actual table are included in the index. Yhe indexes are activated along with the table and are created automatically with it in the database.                    
    6. Difference between transparent tables and pooled tables.- Transparent tables: Transparent tables in the dictionary has a one-to-one relation with the table in database. Its structure corresponds to single database field. Table in the database has the same name as in the dictionary. Transparent table holds application data. Pooled tables. Pooled tables in the dictionary has a many-to-one relation with the table in database. Table in the database has the different name as in the dictionary. Pooled table are stored in table pool at the database level.                    
    7. What is an ABAP/4 Query?- ABAP/4 Query is a powerful tool to generate simple reports without any coding. ABAP/4 Query can generate the following 3 simple reports: Basic List: It is the simple reports. Statistics: Reports with statistical functions like Average, Percentages. Ranked Lists: For analytical reports. - For creating a ABAP/4 Query, programmer has to create user group and a functional group. Functional group can be created using with or without logical database table. Finally, assign user group to functional group. Finally, create a query on the functional group generated.                    
    8. What is BDC programming?- Transferring of large/external/legacy data into SAP system using Batch Input programming. Batch input is a automatic procedure referred to as BDC(Batch Data Communications).The central component of the transfer is a queue file which receives the data vie a batch input programs and groups associated data into "sessions".                    
    9. What are the functional modules used in sequence in BDC?- These are the 3 functional modules which are used in a sequence to perform a data transfer successfully using BDC programming: BDC_OPEN_GROUP - Parameters like Name of the client, sessions and user name are specified in this functional modules. BDC_INSERT - It is used to insert the data for one transaction into a session. BDC_CLOSE_GROUP - This is used to close the batch input session.                    
    10. What are internal tables?- Internal tables are a standard data type object which exists only during the runtime of the program. They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.                    
    11. What is ITS? What are the merits of ITS?- ITS is a Internet Transaction Server. ITS forms an interface between HTTP server and R/3 system, which converts screen provided data by the R/3 system into HTML documents and vice-versa. Merits of ITS: A complete web transaction can be developed and tested in R/3 system. All transaction components, including those used by the ITS outside the R/3 system at runtime, can be stored in the R/3 system. The advantage of automatic language processing in the R/3 system can be utilized to language-dependent HTML documents at runtime.                    
    12. What is DynPro?- DynPro is a Dynamic Programming which is a combination of screen and the associated flow logic Screen is also called as DynPro.
    13. What are screen painter and menu painter?- Screen painter: Screen painter is a tool to design and maintain screen and its elements. It allows user to create GUI screens for the transactions. Attributes, layout, filed attributes and flow logic are the elements of Screen painter. Menu painter: Menu painter is a tool to design the interface components. Status, menu bars, menu lists, F-key settings, functions and titles are the components of Menu painters. Screen painter and menu painter both are the graphical interface of an ABAP/4 applications.
    14. What are the components of SAP scripts?- SAP scripts is a word processing tool of SAP which has the following components: Standard text. It is like a standard normal documents. Layout sets. - Layout set consists of the following components: Windows and pages, Paragraph formats, Character formats. Creating forms in the R/3 system. Every layout set consists of Header, paragraph, and character string. ABAP/4 program.
    15. What is ALV programming in ABAP? When is this grid used in ABAP?- ALV is Application List viewer. Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain up to 90 columns in the display with the wide array of display options.
    16. What are the events in ABAP/4 language?- Initialization, At selection-screen, Start-of-selection, end-of-selection, top-of-page, end-of-page, At line-selection, At user-command, At PF, Get, At New, At LAST, AT END, AT FIRST.
    17. What is CTS and what do you know about it?- The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems and clients in your system landscape. This documentation provides you with an overview of how to manage changes with the CTS and essential information on setting up your system and client landscape and deciding on a transport strategy. Read and follow this documentation when planning your development project.
    18. What are logical databases? What are the advantages/ dis-advantages of logical databases?- To read data from a database tables we use logical database. A logical database provides read-only access to a group of related tables to an ABAP/4 program. Advantages: i)check functions which check that user input is complete, correct,and plausible. ii)Meaningful data selection. iii)central authorization checks for database accesses. iv)good read access performance while retaining the hierarchical data view determined by the application logic. dis advantages: i)If you donot specify a logical database in the program attributes,the GET events never occur. ii)There is no ENDGET command,so the code block associated with an event ends with the next event statement (such as another GET or an END-OF-SELECTION).
    19. What is a batch input session?- BATCH INPUT SESSION is an intermediate step between internal table and database table. Data along with the action is stored in session ie data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.
    20. How to upload data using CATT ?- These are the steps to be followed to Upload data through CATT: Creation of the CATT test case & recording the sample data input. Download of the source file template. Modification of the source file. Upload of the data from the source file.
    21. What is Smart Forms?- Smart Forms allows you to create forms using a graphical design tool with robust functionality, color, and more. Additionally, all new forms developed at SAP will be created with the new Smart Form solution.
    22. How can I make a differentiation between dependent and independent data?- Client dependent or independent transfer requirements include client specific or cross client objects in the change requests. Workbench objects like SAPscripts are client specific, some entries in customizing are client independent. If you display the object list for one change request, and then for each object the object attributes, you will find the flag client specific. If one object in the task list has this flag on, then that transport will be client dependent.
    23. What is the difference between macro and subroutine? - Macros can only be used in the program the are defined in and only after the definition are expanded at compilation / generation. Subroutines (FORM) can be called from both the program the are defined in and other programs . A MACRO is more or less an abbreviation for some lines of code that are used more than once or twice. A FORM is a local subroutine (which can be called external). A FUNCTION is (more or less) a subroutine that is called external. Since debugging a MACRO is not really possible, prevent the use of them (I've never used them, but seen them in action). If the subroutine is used only local (called internal) use a FORM. If the subroutine is called external (used by more than one program) use a FUNCTION.
    Rajiv

  • SAP Latest Software Version for ERP

    Guys,
    I am out of touch with SAP terminologies from long and getting confused when searching forums. Can someone help me here?
    I remember SAP ERP use to be, SAP 4.6c->SAP 4.7->SAP ECC5.0->SAP ECC6.0....which one is the latest? ECC6.0 or it is again called as r/3 now?
    Thanks,
    Z*
    Moderator: It's a joke, isn't it?

    Actually as long as this was posted in the coffee corner in the first place I don't think this question is a joke.  SAP's Product Naming and Numbering scheme is a cruel joke played on customers.
    Technically I think the latest version would be Business Suite 7 innovations 2010 with ERP being at EHP5.  However that's my best guess as honestly I wish either the developers or marketing would final decide who gets to name products and stick with one group naming and numbering products.
    My personal favorites was the whole (s) scheme for releases.  Netweaver 2004s, CRM 2006s, etc.  The going by development year of the product was probably easiest (ERP 2005, CRM 2007), but incremental numbers are probably the easier solution instead.
    It would be great if SAP could resync all the release numbers for the business suite up to a common version.  It's to bad that SAP can't come up with a Business Suite 8 that solves all the version numbers, unless that is being saved for a major overhaul and will unfortuantely probably run on Netweaver 10.
    Take care,
    Stephen

  • SAP latest patch

    Hi,
    I want to check whether the latest patch has been released by SAP so that it can be applied.
    Where can I find it

    ans

  • Hi sap master plz solve my requirement

    hi
    masters
    my client watns a requirement
    in g/l line item display(fbl3n) he wants the offsetting account no or long text
    plz give me the answer
    thank you

    Hi,
    in fbl3n execute
    then it will display report in that select layout and select offestting entry so if data is there it will display
    If it is usefull please assign points
    Thanks
    Ram

  • Hi sap experts plz send me sap fico faqs

    this is my mail id:: [email protected]

    Sriram:
    You can simply google it. Believe me it works!
    http://www.google.com/search?hl=en&q=sapfifaq
    www.sap-img.com/financial/fi-faq.htm
    Vj

  • Error in J2EE WAS 2004s Upgrade from SP04 to SP07

    Hi All,
    When I try to upgrade the WAS Engine from SP04 to SP07 NW2004s I get the error enclosed below:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[F:\usr\sap\P02\JC01\SDM\program\log\sdmcl20060531144655.log]/>
    <!PATTERN[sdmcl20060531144655.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    May 31, 2006 10:46:55... Info: Sync all deployed components with the system component version store.
    May 31, 2006 10:46:55... Info: caf/metamodel/lib: Sync deployment...
    May 31, 2006 10:46:55... Info: caf/metamodel/lib: Component: development component 'caf/metamodel/lib'/'sap.com'/'MAIN_APL70P04_C'/'145084'
    May 31, 2006 10:46:55... Info: caf/metamodel/lib: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\metamodel\lib\MAIN_APL70P04_C\145084\sap.com_cafmetamodellib.sda
    May 31, 2006 10:46:55... Info: caf/metamodel/lib: full component: vendor: 'sap.com', name: 'caf/metamodel/lib', location: 'MAIN_APL70P04_C', counter: '145084
    May 31, 2006 10:46:55... Info: caf/metamodel/lib: updating system component version store...
    May 31, 2006 10:46:55... Info: com.sap.netweaver.coll.appl.gw: Sync deployment...
    May 31, 2006 10:46:55... Info: com.sap.netweaver.coll.appl.gw: Component: development component 'com.sap.netweaver.coll.appl.gw'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:55... Info: com.sap.netweaver.coll.appl.gw: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.netweaver.coll.appl.gw\SAP AG\7.0004.20050922155434.0000\com.sap.netweaver.coll.appl.gw.sda
    May 31, 2006 10:46:55... Info: com.sap.netweaver.coll.appl.gw: full component: vendor: 'sap.com', name: 'com.sap.netweaver.coll.appl.gw', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:55... Info: com.sap.netweaver.coll.appl.gw: updating system component version store...
    May 31, 2006 10:46:55... Info: caf/eu/gp/ui/wdapi: Sync deployment...
    May 31, 2006 10:46:55... Info: caf/eu/gp/ui/wdapi: Component: development component 'caf/eu/gp/ui/wdapi'/'sap.com'/'MAIN_APL70P04_C'/'145188'
    May 31, 2006 10:46:55... Info: caf/eu/gp/ui/wdapi: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\gp\ui\wdapi\MAIN_APL70P04_C\145188\sap.com_cafeugpuiwdapi.sda
    May 31, 2006 10:46:55... Info: caf/eu/gp/ui/wdapi: full component: vendor: 'sap.com', name: 'caf/eu/gp/ui/wdapi', location: 'MAIN_APL70P04_C', counter: '145188
    May 31, 2006 10:46:55... Info: caf/eu/gp/ui/wdapi: updating system component version store...
    May 31, 2006 10:46:55... Info: sqlmap: Sync deployment...
    May 31, 2006 10:46:55... Info: sqlmap: Component: development component 'sqlmap'/'sap.com'/'SAP AG'/'7.0004.20050713131929.0000'
    May 31, 2006 10:46:55... Info: sqlmap: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\sqlmap\SAP AG\7.0004.20050713131929.0000\sqlmap.sda
    May 31, 2006 10:46:55... Info: sqlmap: full component: vendor: 'sap.com', name: 'sqlmap', location: 'SAP AG', counter: '7.0004.20050713131929.0000
    May 31, 2006 10:46:55... Info: sqlmap: updating system component version store...
    May 31, 2006 10:46:55... Info: caf/UI/km/cleanjobadmin: Sync deployment...
    May 31, 2006 10:46:55... Info: caf/UI/km/cleanjobadmin: Component: development component 'caf/UI/km/cleanjobadmin'/'sap.com'/'MAIN_APL70P04_C'/'145461'
    May 31, 2006 10:46:55... Info: caf/UI/km/cleanjobadmin: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\km\cleanjobadmin\MAIN_APL70P04_C\145461\sap.com_cafUIkm~cleanjobadmin.sda
    May 31, 2006 10:46:55... Info: caf/UI/km/cleanjobadmin: full component: vendor: 'sap.com', name: 'caf/UI/km/cleanjobadmin', location: 'MAIN_APL70P04_C', counter: '145461
    May 31, 2006 10:46:55... Info: caf/UI/km/cleanjobadmin: updating system component version store...
    May 31, 2006 10:46:55... Info: com.sap.lcr.saprfc: Sync deployment...
    May 31, 2006 10:46:55... Info: com.sap.lcr.saprfc: Component: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'7.0004.20050802105913.0000'
    May 31, 2006 10:46:55... Info: com.sap.lcr.saprfc: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.lcr.saprfc\SAP AG\7.0004.20050802105913.0000\lcrsaprfc.ear
    May 31, 2006 10:46:55... Info: com.sap.lcr.saprfc: full component: vendor: 'sap.com', name: 'com.sap.lcr.saprfc', location: 'SAP AG', counter: '7.0004.20050802105913.0000
    May 31, 2006 10:46:55... Info: com.sap.lcr.saprfc: updating system component version store...
    May 31, 2006 10:46:55... Info: CAF: Sync deployment...
    May 31, 2006 10:46:55... Info: CAF: Component: software component 'CAF'/'sap.com'/'MAIN_APL70P04_C'/'1000.7.00.4.1.20051007083622'
    May 31, 2006 10:46:55... Error: CAF: Location of software component 'CAF'/'sap.com'/'MAIN_APL70P04_C'/'1000.7.00.4.1.20051007083622' unknown.
    May 31, 2006 10:46:55... Error: CAF: system component version store not updated.
    May 31, 2006 10:46:55... Info: caf/runtime/connectivity: Sync deployment...
    May 31, 2006 10:46:55... Info: caf/runtime/connectivity: Component: development component 'caf/runtime/connectivity'/'sap.com'/'MAIN_APL70P04_C'/'145087'
    May 31, 2006 10:46:55... Info: caf/runtime/connectivity: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\runtime\connectivity\MAIN_APL70P04_C\145087\sap.com_cafruntimeconnectivity.sda
    May 31, 2006 10:46:55... Info: caf/runtime/connectivity: full component: vendor: 'sap.com', name: 'caf/runtime/connectivity', location: 'MAIN_APL70P04_C', counter: '145087
    May 31, 2006 10:46:56... Info: caf/runtime/connectivity: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.aii.util.rb: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.aii.util.rb: Component: development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'7.0004.20050509165220.0000'
    May 31, 2006 10:46:56... Info: com.sap.aii.util.rb: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\7.0004.20050509165220.0000\aii_util_rb.sda
    May 31, 2006 10:46:56... Info: com.sap.aii.util.rb: full component: vendor: 'sap.com', name: 'com.sap.aii.util.rb', location: 'SAP AG', counter: '7.0004.20050509165220.0000
    May 31, 2006 10:46:56... Info: com.sap.aii.util.rb: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.portal.runtime.admin.log: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.portal.runtime.admin.log: Component: development component 'com.sap.portal.runtime.admin.log'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:56... Info: com.sap.portal.runtime.admin.log: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.runtime.admin.log\SAP AG\7.0004.20050921183647.0000\com.sapportals.prt.admin.sda
    May 31, 2006 10:46:56... Info: com.sap.portal.runtime.admin.log: full component: vendor: 'sap.com', name: 'com.sap.portal.runtime.admin.log', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:56... Info: com.sap.portal.runtime.admin.log: updating system component version store...
    May 31, 2006 10:46:56... Info: DocumentServicesLicenseSupportService: Sync deployment...
    May 31, 2006 10:46:56... Info: DocumentServicesLicenseSupportService: Component: development component 'DocumentServicesLicenseSupportService'/'com.adobe'/'Adobe Systems'/'700.20050511161941.198898'
    May 31, 2006 10:46:56... Info: DocumentServicesLicenseSupportService: File location: F:\usr\sap\P02\JC01\SDM\root\origin\com.adobe\DocumentServicesLicenseSupportService\Adobe Systems\700.20050511161941.198898\adobe-DocumentServicesLicenseSupportService.sda
    May 31, 2006 10:46:56... Info: DocumentServicesLicenseSupportService: full component: vendor: 'com.adobe', name: 'DocumentServicesLicenseSupportService', location: 'Adobe Systems', counter: '700.20050511161941.198898
    May 31, 2006 10:46:56... Info: DocumentServicesLicenseSupportService: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/core/dict: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/core/dict: Component: development component 'caf/core/dict'/'sap.com'/'MAIN_APL70P04_C'/'144981'
    May 31, 2006 10:46:56... Info: caf/core/dict: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\core\dict\MAIN_APL70P04_C\144981\sap.com_cafcoredict.sda
    May 31, 2006 10:46:56... Info: caf/core/dict: full component: vendor: 'sap.com', name: 'caf/core/dict', location: 'MAIN_APL70P04_C', counter: '144981
    May 31, 2006 10:46:56... Info: caf/core/dict: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/UI/ptn/classification: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/UI/ptn/classification: Component: development component 'caf/UI/ptn/classification'/'sap.com'/'MAIN_APL70P04_C'/'145466'
    May 31, 2006 10:46:56... Info: caf/UI/ptn/classification: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\classification\MAIN_APL70P04_C\145466\sap.com_cafUIptn~classification.sda
    May 31, 2006 10:46:56... Info: caf/UI/ptn/classification: full component: vendor: 'sap.com', name: 'caf/UI/ptn/classification', location: 'MAIN_APL70P04_C', counter: '145466
    May 31, 2006 10:46:56... Info: caf/UI/ptn/classification: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/sec/ume/wd/batch: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/sec/ume/wd/batch: Component: development component 'tc/sec/ume/wd/batch'/'sap.com'/'MAIN_APL70P04_C'/'145143'
    May 31, 2006 10:46:56... Info: tc/sec/ume/wd/batch: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\sec\ume\wd\batch\MAIN_APL70P04_C\145143\sap.com_tcsecumewdbatch.sda
    May 31, 2006 10:46:56... Info: tc/sec/ume/wd/batch: full component: vendor: 'sap.com', name: 'tc/sec/ume/wd/batch', location: 'MAIN_APL70P04_C', counter: '145143
    May 31, 2006 10:46:56... Info: tc/sec/ume/wd/batch: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/eap: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/eap: Component: development component 'caf/eu/gp/model/eap'/'sap.com'/'MAIN_APL70P04_C'/'145238'
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/eap: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\gp\model\eap\MAIN_APL70P04_C\145238\sap.com_cafeugpmodeleap.sda
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/eap: full component: vendor: 'sap.com', name: 'caf/eu/gp/model/eap', location: 'MAIN_APL70P04_C', counter: '145238
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/eap: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.ip.bi.sdk.dac.connector.checkj: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.ip.bi.sdk.dac.connector.checkj: Component: development component 'com.sap.ip.bi.sdk.dac.connector.checkj'/'sap.com'/'SAP AG'/'7.0004.20050718164821.0000'
    May 31, 2006 10:46:56... Info: com.sap.ip.bi.sdk.dac.connector.checkj: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.ip.bi.sdk.dac.connector.checkj\SAP AG\7.0004.20050718164821.0000\bi_sdk_jdbc.ear
    May 31, 2006 10:46:56... Info: com.sap.ip.bi.sdk.dac.connector.checkj: full component: vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkj', location: 'SAP AG', counter: '7.0004.20050718164821.0000
    May 31, 2006 10:46:56... Info: com.sap.ip.bi.sdk.dac.connector.checkj: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/je/jmx/wsconnector/sp/sda: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/je/jmx/wsconnector/sp/sda: Component: development component 'tc/je/jmx/wsconnector/sp/sda'/'sap.com'/'MAIN_APL70P04_C'/'145098'
    May 31, 2006 10:46:56... Info: tc/je/jmx/wsconnector/sp/sda: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\je\jmx\wsconnector\sp\sda\MAIN_APL70P04_C\145098\sap.com_tcjejmxwsconnectorsp~sda.sda
    May 31, 2006 10:46:56... Info: tc/je/jmx/wsconnector/sp/sda: full component: vendor: 'sap.com', name: 'tc/je/jmx/wsconnector/sp/sda', location: 'MAIN_APL70P04_C', counter: '145098
    May 31, 2006 10:46:56... Info: tc/je/jmx/wsconnector/sp/sda: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.portal.util.threadreporting: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.portal.util.threadreporting: Component: development component 'com.sap.portal.util.threadreporting'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:56... Info: com.sap.portal.util.threadreporting: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.util.threadreporting\SAP AG\7.0004.20050921183647.0000\com.sap.portal.util.threadreporting.sda
    May 31, 2006 10:46:56... Info: com.sap.portal.util.threadreporting: full component: vendor: 'sap.com', name: 'com.sap.portal.util.threadreporting', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:56... Info: com.sap.portal.util.threadreporting: updating system component version store...
    May 31, 2006 10:46:56... Info: pb_lyt: Sync deployment...
    May 31, 2006 10:46:56... Info: pb_lyt: Component: development component 'pb_lyt'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:56... Info: pb_lyt: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\pb_lyt\SAP AG\7.0004.20050922155434.0000\sap.com~pb_lyt.ear
    May 31, 2006 10:46:56... Info: pb_lyt: full component: vendor: 'sap.com', name: 'pb_lyt', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:56... Info: pb_lyt: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/lm/ctc/ccl/rep/hist/if: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/lm/ctc/ccl/rep/hist/if: Component: development component 'tc/lm/ctc/ccl/rep/hist/if'/'sap.com'/'MAIN_APL70P04_C'/'145020'
    May 31, 2006 10:46:56... Info: tc/lm/ctc/ccl/rep/hist/if: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\ctc\ccl\rep\hist\if\MAIN_APL70P04_C\145020\sap.com_tclmctccclrephistif.sda
    May 31, 2006 10:46:56... Info: tc/lm/ctc/ccl/rep/hist/if: full component: vendor: 'sap.com', name: 'tc/lm/ctc/ccl/rep/hist/if', location: 'MAIN_APL70P04_C', counter: '145020
    May 31, 2006 10:46:56... Info: tc/lm/ctc/ccl/rep/hist/if: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sapportals.iviewserver.http: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sapportals.iviewserver.http: Component: development component 'com.sapportals.iviewserver.http'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:56... Info: com.sapportals.iviewserver.http: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.iviewserver.http\SAP AG\7.0004.20050921183647.0000\com.sapportals.iviewserver.http.sda
    May 31, 2006 10:46:56... Info: com.sapportals.iviewserver.http: full component: vendor: 'sap.com', name: 'com.sapportals.iviewserver.http', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:56... Info: com.sapportals.iviewserver.http: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sapportals.builder.pagebuilder: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sapportals.builder.pagebuilder: Component: development component 'com.sapportals.builder.pagebuilder'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:56... Info: com.sapportals.builder.pagebuilder: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.builder.pagebuilder\SAP AG\7.0004.20050922155434.0000\com.sapportals.builder.pagebuilder.sda
    May 31, 2006 10:46:56... Info: com.sapportals.builder.pagebuilder: full component: vendor: 'sap.com', name: 'com.sapportals.builder.pagebuilder', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:56... Info: com.sapportals.builder.pagebuilder: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/bwfbck/eap: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/bwfbck/eap: Component: development component 'caf/eu/gp/model/bwfbck/eap'/'sap.com'/'MAIN_APL70P04_C'/'145239'
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/bwfbck/eap: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\gp\model\bwfbck\eap\MAIN_APL70P04_C\145239\sap.com_cafeugpmodelbwfbck~eap.sda
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/bwfbck/eap: full component: vendor: 'sap.com', name: 'caf/eu/gp/model/bwfbck/eap', location: 'MAIN_APL70P04_C', counter: '145239
    May 31, 2006 10:46:56... Info: caf/eu/gp/model/bwfbck/eap: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/UI/ptn/reporting: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/UI/ptn/reporting: Component: development component 'caf/UI/ptn/reporting'/'sap.com'/'MAIN_APL70P04_C'/'145429'
    May 31, 2006 10:46:56... Info: caf/UI/ptn/reporting: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\reporting\MAIN_APL70P04_C\145429\sap.com_cafUIptn~reporting.sda
    May 31, 2006 10:46:56... Info: caf/UI/ptn/reporting: full component: vendor: 'sap.com', name: 'caf/UI/ptn/reporting', location: 'MAIN_APL70P04_C', counter: '145429
    May 31, 2006 10:46:56... Info: caf/UI/ptn/reporting: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/UI/ptn/flextree: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/UI/ptn/flextree: Component: development component 'caf/UI/ptn/flextree'/'sap.com'/'MAIN_APL70P04_C'/'145424'
    May 31, 2006 10:46:56... Info: caf/UI/ptn/flextree: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\flextree\MAIN_APL70P04_C\145424\sap.com_cafUIptn~flextree.sda
    May 31, 2006 10:46:56... Info: caf/UI/ptn/flextree: full component: vendor: 'sap.com', name: 'caf/UI/ptn/flextree', location: 'MAIN_APL70P04_C', counter: '145424
    May 31, 2006 10:46:56... Info: caf/UI/ptn/flextree: updating system component version store...
    May 31, 2006 10:46:56... Info: classpath_resolver: Sync deployment...
    May 31, 2006 10:46:56... Info: classpath_resolver: Component: development component 'classpath_resolver'/'sap.com'/'SAP AG'/'7.0004.20050726173455.0000'
    May 31, 2006 10:46:56... Info: classpath_resolver: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\classpath_resolver\SAP AG\7.0004.20050726173455.0000\classpath_resolver.sda
    May 31, 2006 10:46:56... Info: classpath_resolver: full component: vendor: 'sap.com', name: 'classpath_resolver', location: 'SAP AG', counter: '7.0004.20050726173455.0000
    May 31, 2006 10:46:56... Info: classpath_resolver: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/eu/er/ui/rt/comp: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/eu/er/ui/rt/comp: Component: development component 'caf/eu/er/ui/rt/comp'/'sap.com'/'MAIN_APL70P04_C'/'145316'
    May 31, 2006 10:46:56... Info: caf/eu/er/ui/rt/comp: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\er\ui\rt\comp\MAIN_APL70P04_C\145316\sap.com_cafeueruirt~comp.sda
    May 31, 2006 10:46:56... Info: caf/eu/er/ui/rt/comp: full component: vendor: 'sap.com', name: 'caf/eu/er/ui/rt/comp', location: 'MAIN_APL70P04_C', counter: '145316
    May 31, 2006 10:46:56... Info: caf/eu/er/ui/rt/comp: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/lm/ctc/cpi_sda: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/lm/ctc/cpi_sda: Component: development component 'tc/lm/ctc/cpi_sda'/'sap.com'/'MAIN_APL70P04_C'/'145177'
    May 31, 2006 10:46:56... Info: tc/lm/ctc/cpi_sda: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\ctc\cpi_sda\MAIN_APL70P04_C\145177\sap.com_tclmctc~cpi_sda.sda
    May 31, 2006 10:46:56... Info: tc/lm/ctc/cpi_sda: full component: vendor: 'sap.com', name: 'tc/lm/ctc/cpi_sda', location: 'MAIN_APL70P04_C', counter: '145177
    May 31, 2006 10:46:56... Info: tc/lm/ctc/cpi_sda: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.km.db: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.km.db: Component: development component 'com.sap.km.db'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:56... Info: com.sap.km.db: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.km.db\SAP AG\7.0004.20050922155434.0000\com.sap.km.db.sda
    May 31, 2006 10:46:56... Info: com.sap.km.db: full component: vendor: 'sap.com', name: 'com.sap.km.db', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:56... Info: com.sap.km.db: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/km.ep.kmnotifsvc: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/km.ep.kmnotifsvc: Component: development component 'caf/km.ep.kmnotifsvc'/'sap.com'/'MAIN_APL70P04_C'/'145072'
    May 31, 2006 10:46:56... Info: caf/km.ep.kmnotifsvc: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\km.ep.kmnotifsvc\MAIN_APL70P04_C\145072\sap.com_caf~km.ep.kmnotifsvc.sda
    May 31, 2006 10:46:56... Info: caf/km.ep.kmnotifsvc: full component: vendor: 'sap.com', name: 'caf/km.ep.kmnotifsvc', location: 'MAIN_APL70P04_C', counter: '145072
    May 31, 2006 10:46:56... Info: caf/km.ep.kmnotifsvc: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/UI/content/transport: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/UI/content/transport: Component: development component 'caf/UI/content/transport'/'sap.com'/'MAIN_APL70P04_C'/'145439'
    May 31, 2006 10:46:56... Info: caf/UI/content/transport: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\content\transport\MAIN_APL70P04_C\145439\sap.com_cafUIcontent~transport.sda
    May 31, 2006 10:46:56... Info: caf/UI/content/transport: full component: vendor: 'sap.com', name: 'caf/UI/content/transport', location: 'MAIN_APL70P04_C', counter: '145439
    May 31, 2006 10:46:56... Info: caf/UI/content/transport: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/sld/data: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/sld/data: Component: development component 'tc/sld/data'/'sap.com'/'SAP AG'/'7.0004.20050802105913.0000'
    May 31, 2006 10:46:56... Info: tc/sld/data: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\sld\data\SAP AG\7.0004.20050802105913.0000\lcrwork.sda
    May 31, 2006 10:46:56... Info: tc/sld/data: full component: vendor: 'sap.com', name: 'tc/sld/data', location: 'SAP AG', counter: '7.0004.20050802105913.0000
    May 31, 2006 10:46:56... Info: tc/sld/data: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/performance/viewer/wd: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/performance/viewer/wd: Component: development component 'tc/lm/webadmin/performance/viewer/wd'/'sap.com'/'MAIN_APL70P04_C'/'145472'
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/performance/viewer/wd: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\webadmin\performance\viewer\wd\MAIN_APL70P04_C\145472\sap.com_tclmwebadminperformanceviewer~wd.sda
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/performance/viewer/wd: full component: vendor: 'sap.com', name: 'tc/lm/webadmin/performance/viewer/wd', location: 'MAIN_APL70P04_C', counter: '145472
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/performance/viewer/wd: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/sld/sldclient_sda: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/sld/sldclient_sda: Component: development component 'tc/sld/sldclient_sda'/'sap.com'/'SAP AG'/'7.0004.20050802105913.0000'
    May 31, 2006 10:46:56... Info: tc/sld/sldclient_sda: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\sld\sldclient_sda\SAP AG\7.0004.20050802105913.0000\sldclient.sda
    May 31, 2006 10:46:56... Info: tc/sld/sldclient_sda: full component: vendor: 'sap.com', name: 'tc/sld/sldclient_sda', location: 'SAP AG', counter: '7.0004.20050802105913.0000
    May 31, 2006 10:46:56... Info: tc/sld/sldclient_sda: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/monitoring/logviewer-standalone: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/monitoring/logviewer-standalone: Component: development component 'tc/monitoring/logviewer-standalone'/'sap.com'/'SAP AG'/'7.0007.20060210155706.0000'
    May 31, 2006 10:46:56... Info: tc/monitoring/logviewer-standalone: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\monitoring\logviewer-standalone\SAP AG\7.0007.20060210155706.0000\logviewer-standalone-fs.sda
    May 31, 2006 10:46:56... Info: tc/monitoring/logviewer-standalone: full component: vendor: 'sap.com', name: 'tc/monitoring/logviewer-standalone', location: 'SAP AG', counter: '7.0007.20060210155706.0000
    May 31, 2006 10:46:56... Info: tc/monitoring/logviewer-standalone: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/apptrace/wd: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/apptrace/wd: Component: development component 'tc/lm/webadmin/apptrace/wd'/'sap.com'/'MAIN_APL70P04_C'/'145357'
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/apptrace/wd: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\webadmin\apptrace\wd\MAIN_APL70P04_C\145357\sap.com_tclmwebadminapptracewd.sda
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/apptrace/wd: full component: vendor: 'sap.com', name: 'tc/lm/webadmin/apptrace/wd', location: 'MAIN_APL70P04_C', counter: '145357
    May 31, 2006 10:46:56... Info: tc/lm/webadmin/apptrace/wd: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.netweaver.bc.logging: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.netweaver.bc.logging: Component: development component 'com.sap.netweaver.bc.logging'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:56... Info: com.sap.netweaver.bc.logging: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.netweaver.bc.logging\SAP AG\7.0004.20050922155434.0000\com.sap.netweaver.bc.logging.ear
    May 31, 2006 10:46:56... Info: com.sap.netweaver.bc.logging: full component: vendor: 'sap.com', name: 'com.sap.netweaver.bc.logging', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:56... Info: com.sap.netweaver.bc.logging: updating system component version store...
    May 31, 2006 10:46:56... Info: tc/sld/wd/businesssystem: Sync deployment...
    May 31, 2006 10:46:56... Info: tc/sld/wd/businesssystem: Component: development component 'tc/sld/wd/businesssystem'/'sap.com'/'MAIN_APL70P04_C'/'145119'
    May 31, 2006 10:46:56... Info: tc/sld/wd/businesssystem: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\sld\wd\businesssystem\MAIN_APL70P04_C\145119\sap.com_tcsldwd~businesssystem.sda
    May 31, 2006 10:46:56... Info: tc/sld/wd/businesssystem: full component: vendor: 'sap.com', name: 'tc/sld/wd/businesssystem', location: 'MAIN_APL70P04_C', counter: '145119
    May 31, 2006 10:46:56... Info: tc/sld/wd/businesssystem: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.portal.logviewer620: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.portal.logviewer620: Component: development component 'com.sap.portal.logviewer620'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:56... Info: com.sap.portal.logviewer620: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.logviewer620\SAP AG\7.0004.20050922155434.0000\com.sap.portal.logviewer620.sda
    May 31, 2006 10:46:56... Info: com.sap.portal.logviewer620: full component: vendor: 'sap.com', name: 'com.sap.portal.logviewer620', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:56... Info: com.sap.portal.logviewer620: updating system component version store...
    May 31, 2006 10:46:56... Info: activation: Sync deployment...
    May 31, 2006 10:46:56... Info: activation: Component: development component 'activation'/'sap.com'/'SAP AG'/'7.0004.20050726173455.0000'
    May 31, 2006 10:46:56... Info: activation: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\activation\SAP AG\7.0004.20050726173455.0000\activation.sda
    May 31, 2006 10:46:56... Info: activation: full component: vendor: 'sap.com', name: 'activation', location: 'SAP AG', counter: '7.0004.20050726173455.0000
    May 31, 2006 10:46:56... Info: activation: updating system component version store...
    May 31, 2006 10:46:56... Info: com.sap.portal.epsolman: Sync deployment...
    May 31, 2006 10:46:56... Info: com.sap.portal.epsolman: Component: development component 'com.sap.portal.epsolman'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:56... Info: com.sap.portal.epsolman: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.epsolman\SAP AG\7.0004.20050922155434.0000\com.sap.portal.epsolman.sda
    May 31, 2006 10:46:56... Info: com.sap.portal.epsolman: full component: vendor: 'sap.com', name: 'com.sap.portal.epsolman', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:56... Info: com.sap.portal.epsolman: updating system component version store...
    May 31, 2006 10:46:56... Info: caf/bw/ear: Sync deployment...
    May 31, 2006 10:46:56... Info: caf/bw/ear: Component: development component 'caf/bw/ear'/'sap.com'/'MAIN_APL70P04_C'/'145335'
    May 31, 2006 10:46:56... Info: caf/bw/ear: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\bw\ear\MAIN_APL70P04_C\145335\sap.com_cafbwear.sda
    May 31, 2006 10:46:56... Info: caf/bw/ear: full component: vendor: 'sap.com', name: 'caf/bw/ear', location: 'MAIN_APL70P04_C', counter: '145335
    May 31, 2006 10:46:56... Info: caf/bw/ear: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/historylog: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/historylog: Component: development component 'caf/UI/ptn/historylog'/'sap.com'/'MAIN_APL70P04_C'/'145427'
    May 31, 2006 10:46:57... Info: caf/UI/ptn/historylog: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\historylog\MAIN_APL70P04_C\145427\sap.com_cafUIptn~historylog.sda
    May 31, 2006 10:46:57... Info: caf/UI/ptn/historylog: full component: vendor: 'sap.com', name: 'caf/UI/ptn/historylog', location: 'MAIN_APL70P04_C', counter: '145427
    May 31, 2006 10:46:57... Info: caf/UI/ptn/historylog: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.pageeditor: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.pageeditor: Component: development component 'com.sapportals.appdesigner.pageeditor'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.pageeditor: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.appdesigner.pageeditor\SAP AG\7.0004.20050922155434.0000\com.sapportals.appdesigner.pageeditor.sda
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.pageeditor: full component: vendor: 'sap.com', name: 'com.sapportals.appdesigner.pageeditor', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.pageeditor: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/eu/es/ui: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/eu/es/ui: Component: development component 'caf/eu/es/ui'/'sap.com'/'MAIN_APL70P04_C'/'145137'
    May 31, 2006 10:46:57... Info: caf/eu/es/ui: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\es\ui\MAIN_APL70P04_C\145137\sap.com_cafeues~ui.sda
    May 31, 2006 10:46:57... Info: caf/eu/es/ui: full component: vendor: 'sap.com', name: 'caf/eu/es/ui', location: 'MAIN_APL70P04_C', counter: '145137
    May 31, 2006 10:46:57... Info: caf/eu/es/ui: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sapportals.utilities.analyzer: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sapportals.utilities.analyzer: Component: development component 'com.sapportals.utilities.analyzer'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:57... Info: com.sapportals.utilities.analyzer: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.utilities.analyzer\SAP AG\7.0004.20050921183647.0000\com.sapportals.utilities.analyzer.sda
    May 31, 2006 10:46:57... Info: com.sapportals.utilities.analyzer: full component: vendor: 'sap.com', name: 'com.sapportals.utilities.analyzer', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:57... Info: com.sapportals.utilities.analyzer: updating system component version store...
    May 31, 2006 10:46:57... Info: EP-WDC: Sync deployment...
    May 31, 2006 10:46:57... Info: EP-WDC: Component: software component 'EP-WDC'/'sap.com'/'SAP AG'/'1000.7.00.4.1.20050922182300'
    May 31, 2006 10:46:57... Info: EP-WDC: File location: F:\usr\sap\P02\JC01\SDM\root\origin_sc\sap.com\EP-WDC\SAP AG\1000.7.00.4.1.20050922182300\EPWDC04_1.SCA
    May 31, 2006 10:46:57... Info: EP-WDC: full component: vendor: 'sap.com', name: 'EP-WDC', location: 'SAP AG', counter: '1000.7.00.4.1.20050922182300
    May 31, 2006 10:46:57... Info: EP-WDC: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/searchbar: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/searchbar: Component: development component 'caf/UI/ptn/searchbar'/'sap.com'/'MAIN_APL70P04_C'/'145430'
    May 31, 2006 10:46:57... Info: caf/UI/ptn/searchbar: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\searchbar\MAIN_APL70P04_C\145430\sap.com_cafUIptn~searchbar.sda
    May 31, 2006 10:46:57... Info: caf/UI/ptn/searchbar: full component: vendor: 'sap.com', name: 'caf/UI/ptn/searchbar', location: 'MAIN_APL70P04_C', counter: '145430
    May 31, 2006 10:46:57... Info: caf/UI/ptn/searchbar: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.netweaver.bc.wf.db: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.netweaver.bc.wf.db: Component: development component 'com.sap.netweaver.bc.wf.db'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sap.netweaver.bc.wf.db: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.netweaver.bc.wf.db\SAP AG\7.0004.20050922155434.0000\com.sap.netweaver.bc.wf.db.sda
    May 31, 2006 10:46:57... Info: com.sap.netweaver.bc.wf.db: full component: vendor: 'sap.com', name: 'com.sap.netweaver.bc.wf.db', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sap.netweaver.bc.wf.db: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/eu/gp/model/jmx/eap: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/eu/gp/model/jmx/eap: Component: development component 'caf/eu/gp/model/jmx/eap'/'sap.com'/'MAIN_APL70P04_C'/'145377'
    May 31, 2006 10:46:57... Info: caf/eu/gp/model/jmx/eap: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\gp\model\jmx\eap\MAIN_APL70P04_C\145377\sap.com_cafeugpmodeljmx~eap.sda
    May 31, 2006 10:46:57... Info: caf/eu/gp/model/jmx/eap: full component: vendor: 'sap.com', name: 'caf/eu/gp/model/jmx/eap', location: 'MAIN_APL70P04_C', counter: '145377
    May 31, 2006 10:46:57... Info: caf/eu/gp/model/jmx/eap: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/admin/wd: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/admin/wd: Component: development component 'tc/lm/webadmin/application/admin/wd'/'sap.com'/'MAIN_APL70P04_C'/'145353'
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/admin/wd: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\webadmin\application\admin\wd\MAIN_APL70P04_C\145353\sap.com_tclmwebadminapplicationadmin~wd.sda
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/admin/wd: full component: vendor: 'sap.com', name: 'tc/lm/webadmin/application/admin/wd', location: 'MAIN_APL70P04_C', counter: '145353
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/admin/wd: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/overview/debug/wd: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/overview/debug/wd: Component: development component 'tc/lm/webadmin/overview/debug/wd'/'sap.com'/'MAIN_APL70P04_C'/'145346'
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/overview/debug/wd: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\webadmin\overview\debug\wd\MAIN_APL70P04_C\145346\sap.com_tclmwebadminoverviewdebug~wd.sda
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/overview/debug/wd: full component: vendor: 'sap.com', name: 'tc/lm/webadmin/overview/debug/wd', location: 'MAIN_APL70P04_C', counter: '145346
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/overview/debug/wd: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sapportals.builder.portallayouts: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sapportals.builder.portallayouts: Component: development component 'com.sapportals.builder.portallayouts'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sapportals.builder.portallayouts: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.builder.portallayouts\SAP AG\7.0004.20050922155434.0000\com.sapportals.builder.portallayouts.sda
    May 31, 2006 10:46:57... Info: com.sapportals.builder.portallayouts: full component: vendor: 'sap.com', name: 'com.sapportals.builder.portallayouts', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sapportals.builder.portallayouts: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.security.core.sda: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.security.core.sda: Component: development component 'com.sap.security.core.sda'/'sap.com'/'SAP AG'/'7.0004.20050818101701.0000'
    May 31, 2006 10:46:57... Info: com.sap.security.core.sda: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.security.core.sda\SAP AG\7.0004.20050818101701.0000\com.sap.security.core.offline.sda
    May 31, 2006 10:46:57... Info: com.sap.security.core.sda: full component: vendor: 'sap.com', name: 'com.sap.security.core.sda', location: 'SAP AG', counter: '7.0004.20050818101701.0000
    May 31, 2006 10:46:57... Info: com.sap.security.core.sda: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.km.application: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.km.application: Component: development component 'com.sap.km.application'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sap.km.application: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.km.application\SAP AG\7.0004.20050922155434.0000\com.sap.km.application.sda
    May 31, 2006 10:46:57... Info: com.sap.km.application: full component: vendor: 'sap.com', name: 'com.sap.km.application', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sap.km.application: updating system component version store...
    May 31, 2006 10:46:57... Info: shell_api: Sync deployment...
    May 31, 2006 10:46:57... Info: shell_api: Component: development component 'shell_api'/'sap.com'/'SAP AG'/'7.0004.20050726173455.0000'
    May 31, 2006 10:46:57... Info: shell_api: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\shell_api\SAP AG\7.0004.20050726173455.0000\shell_api.sda
    May 31, 2006 10:46:57... Info: shell_api: full component: vendor: 'sap.com', name: 'shell_api', location: 'SAP AG', counter: '7.0004.20050726173455.0000
    May 31, 2006 10:46:57... Info: shell_api: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectbrowser: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectbrowser: Component: development component 'caf/UI/ptn/objectbrowser'/'sap.com'/'MAIN_APL70P04_C'/'145431'
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectbrowser: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\objectbrowser\MAIN_APL70P04_C\145431\sap.com_cafUIptn~objectbrowser.sda
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectbrowser: full component: vendor: 'sap.com', name: 'caf/UI/ptn/objectbrowser', location: 'MAIN_APL70P04_C', counter: '145431
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectbrowser: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectselector: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectselector: Component: development component 'caf/UI/ptn/objectselector'/'sap.com'/'MAIN_APL70P04_C'/'145426'
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectselector: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\objectselector\MAIN_APL70P04_C\145426\sap.com_cafUIptn~objectselector.sda
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectselector: full component: vendor: 'sap.com', name: 'caf/UI/ptn/objectselector', location: 'MAIN_APL70P04_C', counter: '145426
    May 31, 2006 10:46:57... Info: caf/UI/ptn/objectselector: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.portal.admin.util: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.portal.admin.util: Component: development component 'com.sap.portal.admin.util'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:57... Info: com.sap.portal.admin.util: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.admin.util\SAP AG\7.0004.20050921183647.0000\com.sap.portal.admin.util.sda
    May 31, 2006 10:46:57... Info: com.sap.portal.admin.util: full component: vendor: 'sap.com', name: 'com.sap.portal.admin.util', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:57... Info: com.sap.portal.admin.util: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.frameworkapi: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.frameworkapi: Component: development component 'com.sapportals.appdesigner.frameworkapi'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.frameworkapi: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.appdesigner.frameworkapi\SAP AG\7.0004.20050921183647.0000\com.sapportals.appdesigner.frameworkapi.sda
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.frameworkapi: full component: vendor: 'sap.com', name: 'com.sapportals.appdesigner.frameworkapi', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:57... Info: com.sapportals.appdesigner.frameworkapi: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.mw.jco: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.mw.jco: Component: development component 'com.sap.mw.jco'/'sap.com'/'SAP AG'/'7.0004.20050812161614.0000'
    May 31, 2006 10:46:57... Info: com.sap.mw.jco: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.mw.jco\SAP AG\7.0004.20050812161614.0000\jrfc.sda
    May 31, 2006 10:46:57... Info: com.sap.mw.jco: full component: vendor: 'sap.com', name: 'com.sap.mw.jco', location: 'SAP AG', counter: '7.0004.20050812161614.0000
    May 31, 2006 10:46:57... Info: com.sap.mw.jco: updating system component version store...
    May 31, 2006 10:46:57... Info: bi/mmr/dictionary: Sync deployment...
    May 31, 2006 10:46:57... Info: bi/mmr/dictionary: Component: development component 'bi/mmr/dictionary'/'sap.com'/'SAP AG'/'7.0004.20050713145506.0000'
    May 31, 2006 10:46:57... Info: bi/mmr/dictionary: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\bi\mmr\dictionary\SAP AG\7.0004.20050713145506.0000\sap.combimmr~dictionary.sda
    May 31, 2006 10:46:57... Info: bi/mmr/dictionary: full component: vendor: 'sap.com', name: 'bi/mmr/dictionary', location: 'SAP AG', counter: '7.0004.20050713145506.0000
    May 31, 2006 10:46:57... Info: bi/mmr/dictionary: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sapportals.iviewserver.appintegrate: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sapportals.iviewserver.appintegrate: Component: development component 'com.sapportals.iviewserver.appintegrate'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sapportals.iviewserver.appintegrate: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.iviewserver.appintegrate\SAP AG\7.0004.20050922155434.0000\com.sapportals.iviewserver.appintegrate.sda
    May 31, 2006 10:46:57... Info: com.sapportals.iviewserver.appintegrate: full component: vendor: 'sap.com', name: 'com.sapportals.iviewserver.appintegrate', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sapportals.iviewserver.appintegrate: updating system component version store...
    May 31, 2006 10:46:57... Info: tc.httpclient: Sync deployment...
    May 31, 2006 10:46:57... Info: tc.httpclient: Component: development component 'tc.httpclient'/'sap.com'/'SAP AG'/'7.0004.20050713132957.0000'
    May 31, 2006 10:46:57... Info: tc.httpclient: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc.httpclient\SAP AG\7.0004.20050713132957.0000\httpclient.sda
    May 31, 2006 10:46:57... Info: tc.httpclient: full component: vendor: 'sap.com', name: 'tc.httpclient', location: 'SAP AG', counter: '7.0004.20050713132957.0000
    May 31, 2006 10:46:57... Info: tc.httpclient: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/bizc/lib: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/bizc/lib: Component: development component 'tc/bizc/lib'/'sap.com'/'SAP AG'/'7.0004.20050509144226.0000'
    May 31, 2006 10:46:57... Info: tc/bizc/lib: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\bizc\lib\SAP AG\7.0004.20050509144226.0000\sap.comtcbizc~lib.sda
    May 31, 2006 10:46:57... Info: tc/bizc/lib: full component: vendor: 'sap.com', name: 'tc/bizc/lib', location: 'SAP AG', counter: '7.0004.20050509144226.0000
    May 31, 2006 10:46:57... Info: tc/bizc/lib: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.portal.dotnet.services.systems: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.portal.dotnet.services.systems: Component: development component 'com.sap.portal.dotnet.services.systems'/'sap.com'/'SAP AG'/'7.0004.20050926131054.0000'
    May 31, 2006 10:46:57... Info: com.sap.portal.dotnet.services.systems: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.dotnet.services.systems\SAP AG\7.0004.20050926131054.0000\com.sap.portal.dotnet.services.systems.sda
    May 31, 2006 10:46:57... Info: com.sap.portal.dotnet.services.systems: full component: vendor: 'sap.com', name: 'com.sap.portal.dotnet.services.systems', location: 'SAP AG', counter: '7.0004.20050926131054.0000
    May 31, 2006 10:46:57... Info: com.sap.portal.dotnet.services.systems: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/mp/mmr/adapter/ear: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/mp/mmr/adapter/ear: Component: development component 'caf/mp/mmr/adapter/ear'/'sap.com'/'MAIN_APL70P04_C'/'145270'
    May 31, 2006 10:46:57... Info: caf/mp/mmr/adapter/ear: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\mp\mmr\adapter\ear\MAIN_APL70P04_C\145270\sap.com_cafmpmmradapterear.sda
    May 31, 2006 10:46:57... Info: caf/mp/mmr/adapter/ear: full component: vendor: 'sap.com', name: 'caf/mp/mmr/adapter/ear', location: 'MAIN_APL70P04_C', counter: '145270
    May 31, 2006 10:46:57... Info: caf/mp/mmr/adapter/ear: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/propedit: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/UI/ptn/propedit: Component: development component 'caf/UI/ptn/propedit'/'sap.com'/'MAIN_APL70P04_C'/'145469'
    May 31, 2006 10:46:57... Info: caf/UI/ptn/propedit: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\UI\ptn\propedit\MAIN_APL70P04_C\145469\sap.com_cafUIptn~propedit.sda
    May 31, 2006 10:46:57... Info: caf/UI/ptn/propedit: full component: vendor: 'sap.com', name: 'caf/UI/ptn/propedit', location: 'MAIN_APL70P04_C', counter: '145469
    May 31, 2006 10:46:57... Info: caf/UI/ptn/propedit: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.mdi: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.mdi: Component: development component 'com.sap.mdi'/'sap.com'/'SAP AG'/'7.0004.20050509171002.0000'
    May 31, 2006 10:46:57... Info: com.sap.mdi: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.mdi\SAP AG\7.0004.20050509171002.0000\SAPmdi.sda
    May 31, 2006 10:46:57... Info: com.sap.mdi: full component: vendor: 'sap.com', name: 'com.sap.mdi', location: 'SAP AG', counter: '7.0004.20050509171002.0000
    May 31, 2006 10:46:57... Info: com.sap.mdi: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/ni: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/ni: Component: development component 'tc/ni'/'sap.com'/'SAP AG'/'7.0004.20050509132302.0000'
    May 31, 2006 10:46:57... Info: tc/ni: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\ni\SAP AG\7.0004.20050509132302.0000\sapni.sda
    May 31, 2006 10:46:57... Info: tc/ni: full component: vendor: 'sap.com', name: 'tc/ni', location: 'SAP AG', counter: '7.0004.20050509132302.0000
    May 31, 2006 10:46:57... Info: tc/ni: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/res/jdbc/wd: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/res/jdbc/wd: Component: development component 'tc/lm/webadmin/application/res/jdbc/wd'/'sap.com'/'MAIN_APL70P04_C'/'145444'
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/res/jdbc/wd: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\webadmin\application\res\jdbc\wd\MAIN_APL70P04_C\145444\sap.com_tclmwebadminapplicationresjdbcwd.sda
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/res/jdbc/wd: full component: vendor: 'sap.com', name: 'tc/lm/webadmin/application/res/jdbc/wd', location: 'MAIN_APL70P04_C', counter: '145444
    May 31, 2006 10:46:57... Info: tc/lm/webadmin/application/res/jdbc/wd: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/sld/wd/classbrowser: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/sld/wd/classbrowser: Component: development component 'tc/sld/wd/classbrowser'/'sap.com'/'MAIN_APL70P04_C'/'145022'
    May 31, 2006 10:46:57... Info: tc/sld/wd/classbrowser: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\sld\wd\classbrowser\MAIN_APL70P04_C\145022\sap.com_tcsldwd~classbrowser.sda
    May 31, 2006 10:46:57... Info: tc/sld/wd/classbrowser: full component: vendor: 'sap.com', name: 'tc/sld/wd/classbrowser', location: 'MAIN_APL70P04_C', counter: '145022
    May 31, 2006 10:46:57... Info: tc/sld/wd/classbrowser: updating system component version store...
    May 31, 2006 10:46:57... Info: tc/lm/ctc/cul/interface_sda: Sync deployment...
    May 31, 2006 10:46:57... Info: tc/lm/ctc/cul/interface_sda: Component: development component 'tc/lm/ctc/cul/interface_sda'/'sap.com'/'MAIN_APL70P04_C'/'145284'
    May 31, 2006 10:46:57... Info: tc/lm/ctc/cul/interface_sda: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\tc\lm\ctc\cul\interface_sda\MAIN_APL70P04_C\145284\sap.com_tclmctcculinterface_sda.sda
    May 31, 2006 10:46:57... Info: tc/lm/ctc/cul/interface_sda: full component: vendor: 'sap.com', name: 'tc/lm/ctc/cul/interface_sda', location: 'MAIN_APL70P04_C', counter: '145284
    May 31, 2006 10:46:57... Info: tc/lm/ctc/cul/interface_sda: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.km.trex.ui: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.km.trex.ui: Component: development component 'com.sap.km.trex.ui'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sap.km.trex.ui: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.km.trex.ui\SAP AG\7.0004.20050922155434.0000\com.sap.km.trex.ui.sda
    May 31, 2006 10:46:57... Info: com.sap.km.trex.ui: full component: vendor: 'sap.com', name: 'com.sap.km.trex.ui', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sap.km.trex.ui: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.rtc: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.rtc: Component: development component 'com.sap.netweaver.coll.appl.rtc'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.rtc: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.netweaver.coll.appl.rtc\SAP AG\7.0004.20050922155434.0000\com.sap.netweaver.coll.appl.rtc.sda
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.rtc: full component: vendor: 'sap.com', name: 'com.sap.netweaver.coll.appl.rtc', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.rtc: updating system component version store...
    May 31, 2006 10:46:57... Info: naming: Sync deployment...
    May 31, 2006 10:46:57... Info: naming: Component: development component 'naming'/'sap.com'/'SAP AG'/'7.0004.20050726173455.0000'
    May 31, 2006 10:46:57... Info: naming: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\naming\SAP AG\7.0004.20050726173455.0000\naming.sda
    May 31, 2006 10:46:57... Info: naming: full component: vendor: 'sap.com', name: 'naming', location: 'SAP AG', counter: '7.0004.20050726173455.0000
    May 31, 2006 10:46:57... Info: naming: updating system component version store...
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.sync: Sync deployment...
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.sync: Component: development component 'com.sap.netweaver.coll.appl.sync'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.sync: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.netweaver.coll.appl.sync\SAP AG\7.0004.20050922155434.0000\com.sap.netweaver.coll.appl.sync.sda
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.sync: full component: vendor: 'sap.com', name: 'com.sap.netweaver.coll.appl.sync', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:57... Info: com.sap.netweaver.coll.appl.sync: updating system component version store...
    May 31, 2006 10:46:57... Info: caf/um/metadata/api: Sync deployment...
    May 31, 2006 10:46:57... Info: caf/um/metadata/api: Component: development component 'caf/um/metadata/api'/'sap.com'/'MAIN_APL70P04_C'/'144975'
    May 31, 2006 10:46:57... Info: caf/um/metadata/api: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\um\metadata\api\MAIN_APL70P04_C\144975\sap.com_cafummetadata~api.sda
    May 31, 2006 10:46:57... Info: caf/um/metadata/api: full component: vendor: 'sap.com', name: 'caf/um/metadata/api', location: 'MAIN_APL70P04_C', counter: '144975
    May 31, 2006 10:46:57... Info: caf/um/metadata/api: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sap.dqe.dbschema: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sap.dqe.dbschema: Component: development component 'com.sap.dqe.dbschema'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:58... Info: com.sap.dqe.dbschema: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.dqe.dbschema\SAP AG\7.0004.20050922155434.0000\com.sap.dqe.dbschema.sda
    May 31, 2006 10:46:58... Info: com.sap.dqe.dbschema: full component: vendor: 'sap.com', name: 'com.sap.dqe.dbschema', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:58... Info: com.sap.dqe.dbschema: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.zorkservice: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.zorkservice: Component: development component 'com.sap.portal.pcd.zorkservice'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.zorkservice: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.pcd.zorkservice\SAP AG\7.0004.20050921183647.0000\com.sap.portal.pcd.zorkservice.sda
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.zorkservice: full component: vendor: 'sap.com', name: 'com.sap.portal.pcd.zorkservice', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.zorkservice: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sapportals.portaladmin.wizframework: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sapportals.portaladmin.wizframework: Component: development component 'com.sapportals.portaladmin.wizframework'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:58... Info: com.sapportals.portaladmin.wizframework: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sapportals.portaladmin.wizframework\SAP AG\7.0004.20050921183647.0000\com.sapportals.portaladmin.wizframework.sda
    May 31, 2006 10:46:58... Info: com.sapportals.portaladmin.wizframework: full component: vendor: 'sap.com', name: 'com.sapportals.portaladmin.wizframework', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:58... Info: com.sapportals.portaladmin.wizframework: updating system component version store...
    May 31, 2006 10:46:58... Info: caf/tc/dictionary: Sync deployment...
    May 31, 2006 10:46:58... Info: caf/tc/dictionary: Component: development component 'caf/tc/dictionary'/'sap.com'/'MAIN_APL70P04_C'/'145086'
    May 31, 2006 10:46:58... Info: caf/tc/dictionary: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\tc\dictionary\MAIN_APL70P04_C\145086\sap.com_caftcdictionary.sda
    May 31, 2006 10:46:58... Info: caf/tc/dictionary: full component: vendor: 'sap.com', name: 'caf/tc/dictionary', location: 'MAIN_APL70P04_C', counter: '145086
    May 31, 2006 10:46:58... Info: caf/tc/dictionary: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sap.portal.strucfilterservice: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sap.portal.strucfilterservice: Component: development component 'com.sap.portal.strucfilterservice'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000'
    May 31, 2006 10:46:58... Info: com.sap.portal.strucfilterservice: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.strucfilterservice\SAP AG\7.0004.20050921183647.0000\com.sap.portal.strucfilterservice.sda
    May 31, 2006 10:46:58... Info: com.sap.portal.strucfilterservice: full component: vendor: 'sap.com', name: 'com.sap.portal.strucfilterservice', location: 'SAP AG', counter: '7.0004.20050921183647.0000
    May 31, 2006 10:46:58... Info: com.sap.portal.strucfilterservice: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sap.km.cm.service: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sap.km.cm.service: Component: development component 'com.sap.km.cm.service'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:58... Info: com.sap.km.cm.service: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.km.cm.service\SAP AG\7.0004.20050922155434.0000\com.sap.km.cm.service.sda
    May 31, 2006 10:46:58... Info: com.sap.km.cm.service: full component: vendor: 'sap.com', name: 'com.sap.km.cm.service', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:58... Info: com.sap.km.cm.service: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.rolemigration: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.rolemigration: Component: development component 'com.sap.portal.pcd.rolemigration'/'sap.com'/'SAP AG'/'7.0004.20050922155434.0000'
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.rolemigration: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.portal.pcd.rolemigration\SAP AG\7.0004.20050922155434.0000\com.sap.portal.pcd.rolemigration.sda
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.rolemigration: full component: vendor: 'sap.com', name: 'com.sap.portal.pcd.rolemigration', location: 'SAP AG', counter: '7.0004.20050922155434.0000
    May 31, 2006 10:46:58... Info: com.sap.portal.pcd.rolemigration: updating system component version store...
    May 31, 2006 10:46:58... Info: caf/eu/gp/ui/search: Sync deployment...
    May 31, 2006 10:46:58... Info: caf/eu/gp/ui/search: Component: development component 'caf/eu/gp/ui/search'/'sap.com'/'MAIN_APL70P04_C'/'145183'
    May 31, 2006 10:46:58... Info: caf/eu/gp/ui/search: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\caf\eu\gp\ui\search\MAIN_APL70P04_C\145183\sap.com_cafeugpuisearch.sda
    May 31, 2006 10:46:58... Info: caf/eu/gp/ui/search: full component: vendor: 'sap.com', name: 'caf/eu/gp/ui/search', location: 'MAIN_APL70P04_C', counter: '145183
    May 31, 2006 10:46:58... Info: caf/eu/gp/ui/search: updating system component version store...
    May 31, 2006 10:46:58... Info: com.sap.sl.ut.jddi.schema: Sync deployment...
    May 31, 2006 10:46:58... Info: com.sap.sl.ut.jddi.schema: Component: development component 'com.sap.sl.ut.jddi.schema'/'sap.com'/'SAP AG'/'7.0004.20050715192903.0000'
    May 31, 2006 10:46:58... Info: com.sap.sl.ut.jddi.schema: File location: F:\usr\sap\P02\JC01\SDM\root\origin\sap.com\com.sap.sl.ut.jddi.schema\SAP AG\7.0004.20050715192903.0000\sap.c

    Hi
    Plz refer the upgrade document
    https://websmp206.sap-ag.de/nw04upgrade
    Check the upgrade strategy from here
    https://websmp206.sap-ag.de/nw04
    meet the pre requsite as defind in
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/77317c8d-0701-0010-f093-ed35a427f559#java04s
    Cheers
    Jawahar Govindaraj
    Message was edited by: Jawahar Govindaraj

  • Plz tel me regarding SAP Internal support

    hi
    sap experts
    plz tel me the
    SAP Internal support

    Hello,
    I would suggest before formulating a question, please go through the web if there is any notes available.
    SAP Solution Manageer has provided all types of tools for Support Activities. I would also recommend you to go through the SAP solution documentation material.
    http://help.sap.com/saphelp_sm310/helpdata/en/13/4807f4fc6f421cb39002c6603d452c/frameset.htm
    Regards,
    Ravi

  • How do I get to know the latest available and compatible versions?

    We are currently running SAP ERP 6.0 EHP 5, SAP EHP 1 for SAP NetWeaver 7.0, Solution Manager 7.0 EHP 1 and SAP EHP 1 for SAP NetWeaver 7.0 respectively for ECC, BI, Solman and Portal. I want to know the latest compatible versions available in SMP in detail for an upgrade. Where do I find this? Please help.

    Hi Sai,
    for your query
    I want to know the latest compatible versions available in SMP in detail for an upgrade. Where do I find this? Please help.
    Which version do you plan to upgrade ?
    You may use SAP tool Upgrade Dependency Analyzer www://service.sap.com/uda
    to check the dependencies in your upgrade.
    Refer PAM for supported OS/DB platform for your target system. www.service.sap.com/PAM
    Refer Master guide , upgrade guide and release notes for latest supported version for your target release.
    Hope this helps
    Regards,
    Deepak Kori

  • Login screen - sap b1

    Dear All,
    We want to display the customer Name & logo in login screen of sap b1. Is it possible ? Request your suggestions please.
    Regards,
    V.Rajesh

    Hi,
    Plz refer to this link.
    Changing the SBO login picture
    Warm Regards.

  • Reg. Accounting Revenues for MTO & MTS in SAP PP

    Hi all,
      I am having few doubts in Costing aspects of SAP PP.
    What is Accounting revenues for MTO & MTS scenario how its to be defined.Please explain?
    What are the Costing impacts of SAP PP.How the Costing of a Product in the production aspects to be addressed.What are the prerequistes for that.Please provide me help materials with detailed examples.
    Thanks in advance,
    M.Badrinarain.

    Dear Badri,
    Plz refer the below link, this is current thread of CO Forum, Reply by Mr. Mangalraj
    [Product Costing;
    Regards
    kumar
    Edited by: kumar kumar on Nov 9, 2009 11:07 AM

  • Travel Mgmt flow in SAP  -- Urgent

    Hi peers
    Just give me an insight of how the process will be in Travel mgmt. if somebody have any flow diagram or sumthing,plz send me. my id is rajaramj1 attherateof yahoo.com
    Regards
    Rajaram

    hi
    plz refer at
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/451e77f6-0d01-0010-4eba-d02d87f37e55
    and also at
    http://download.sap.com/download.epd?context=EDB7D5211C02FD40BB17036F47900464A3980D8E54D92D64C8AC1AF6021DCE9405AA5AF95BF087548E50268A3B1E6424309EF4C041A91F42
    assign points if useful
    regards
    Srilaskhmi

  • How replicate a Contract froma SAP SRM to SAP ECC

    Hi all,
    I created a Global Contract on SRM system. Is there a way to replicate it to SAP ECC? Is there also a way to associate it to an existing Contract in SAP ECC system?
    Thanks very much, Regards,
    Maria

    Hi,
    1. The backend system should be defined (SAP R/3) in your  Technical Settings (SPRO) and RFC destination to R/3 system should be configured
    2. Then the Message Type BLAORD needs to be configured in ALE/IDoc settings.
    Plz refer this thread for more info:
    Problem with contract
    Once this is done, all GOA created inSRM will be replicated to SAP R/3 system.
    Regards
    Kathirvel

Maybe you are looking for

  • Help on Creating Aggregates on MultiProvider

    Hi All, Is it possible to create aggregates on MultiProvider or its possible in Basic Cubes Only. please suggest with that? some document i go through You do not have to create aggregates for MultiCubes. regards babu

  • One iPhone; Multiple Apple IDs

    I have the following - Windows 8; Itunes is loaded with my personal Apple ID; received an Iphone 5 with company Apple ID and permission to load personal apps, etc. on the company phone. How do I load multiple apple id's onto the one phone? I tried sy

  • How do I know if I set up Apple's two factor authentication?

    How can I tell if I ever set up Apple's two factor authentication and should make sure I can find the Recovery Key?

  • How can one remove a raised texture pattern from a scan of the original photo?

    How can one remove a raised texture pattern from a scan of the original photo? Have several wedding photos scanned into PS Elements that were printed by the pro, photography studio on a raised pattern paper. Would anyone know how to remove the honey

  • Edit HTML of initial Variable Screen in WAD

    Hai WAD   Is it possible to edit initial variable screen which I get after publishing it in the browser. Can I change the settings like color,font add logo in the top of the varibale screen? Thx in Advance Rajesh