Roles in implementation

hi,
tell what exactly people do in implementation project.please explain roles clearly.
thanks&regards
anil kumar

Hi,
check these links:
http://help.sap.com/bp_biv335/BI_EN/documentation/BW_ROLES_SKILLS.doc
/people/mary.huang/blog/2005/06/01/bw-project-management-as-a-jigsaw-puzzle
/people/marc.bernard/blog/2005/02/08/follow-me-into-the-world-of-business-intelligence
/people/arunkumar.sampathkumar/blog/2006/09/08/configuring-ep-for-connecting-to-bw
Also check:
http://help.sap.com/bp_biv135/html/index.htm
Go through these links:
http://csc-studentweb.lrc.edu/swp/Berg/articles/Managing%20SAP%20BW%20projects%20part-1%20v7.ppt
http://csc-studentweb.lrc.edu/swp/Berg/articles/Managing%20SAP%20BW%20projects%20part-2%20v15.ppt
Standard business content queries, cubes etc. depending on application you can find here:
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
Responsibilities of an implementation project...
For ex, Lets say If its a fresh implementation of BI or for that matter you are implementing SAP...
First and foremost will be your requirements gathering from the client. Depending upon the requirements you will creat a business blueprint of the project which is the entire process from the start to the end of an implementation...
After the blue print phase sign off we start off with the realization phase where the actual development happens... In our example after installing the necessary softwares, patches for BI we need to discuss with the end users who are going to use the system for inputs like how they want a report to look like and what are the Key Performance Indicators(KPI) for the reports etc., basically its a question and answer session with the business users... After collecting those informations the development happens in the development servers...
After the development comes to an end the same objects are tested in quality servers for any bugs, errors etc., When all the tests are done we move all the objects to the production environment and test it again whether everything works fine...
The Go-Live of the project happens where the actually postings happen from the users and reports are generated based on those inputs which will be available as an analytical report for the management to take decisions...
The responsibilites vary depending on the requirement... Initially the business analyst will interact with the end users/managers etc., then on the requirements the software consultants do the development, testers do the testing and finally the go-live happens...
BW Data Architect
Description
The BW Data Architect is responsible for the overall data design of the BW project. This includes the design of the:
» BW InfoCubes (Basic Cubes, Multi-cubes, Remote cubes, and Aggregates)
» BW ODS Objects
» BW Datamarts
» Logical Models
» BW Process Models
» BW Enterprise Models
The BW Data Architect plays a critical role in the BW project and is the link between the end users business requirements and the data architecture solution that will satisfy these requirements. All other activities in the BW project are contingent upon the data design being sound and flexible enough to satisfy evolving business requirements.
Time Commitment
the time which must be committed to this Role to ensure the project requirements are met
Project Complexity Time Commitment
Low If the BW project utilizes standard BW content and InfoCubes, this role can be satisfied by the BW Application Consultant.
Medium If the BW project requires enhancements to the standard BW content and InfoCubes and/or requires the integration of non-SAP data, this role may require a committed resource.
High If the BW project requires significant modification and enhancement to standard BW content and InfoCubes, it is highly recommended that an experienced resource be committed full-time to the project.
Key Attributes
The BW Data Architect must have:
» An understanding of the BW data architecture
» An understanding of multidimensional modeling
» An understanding of the differences between operational systems data modeling and data warehouse data modeling
» An understanding of the end users data
» An understanding of the integration points of the data (e.g., customer number, invoice number)
» Excellent troubleshooting and analytical skills
» Excellent communication skills
» Technical competency in data modeling
» Multi-language skills, if an international implementation
» Working knowledge of the BW and R/3 application(s)
» Experience with Data Modeling application software (i.e., ERWIN, Oracle Designer, S-Designer, etc.)
Key Tasks
The BW Data Architect is responsible for capturing the business requirements for the BW project. This effort includes:
» Planning the business requirements gathering sessions and process
» Coordinating all business requirements gathering efforts with the BW Project Manager
» Facilitating the business requirements gathering sessions
» Capturing the information and producing the deliverables from the business requirements gathering sessions
» Understanding and documenting business definitions of data
» Developing the data model
» Ensuring integration of data from both SAP and non-SAP sources
» Fielding questions concerning the data content, definition and structure
This role should also address other critical data design issues such as:
» Granularity of data and the potential for multiple levels of granularity
» Use of degenerate dimensions
» InfoCube partitioning
» Need for aggregation at multiple levels
» Need for storing derived BW data
» Ensuring overall integrity of all BW Models
» Providing Data Administration development standards for business requirements analysis and BW enterprise modeling
» Provide strategic planning for data management
» Impact analysis of data change requirements
As stated above, the BW Data Architect is responsible for the overall data design of the BW project. This includes the design of the:
» BW InfoCubes (Basic Cubes, Multi-cubes, Remote cubes, and Aggregates)
» BW ODS Objects
» BW Datamarts
» Logical Models
» BW Process Models
» BW Enterprise Models
BW Project Implementation and Rollout
Global IDs uses a modified version of the ASAP methodology to ensure a robust BW environment is implemented, tested, and delivered. The project milestones include the following:
Blueprinting
Realization
Roll Out
Post-Implementation Support
Organizational Change Management
BW Maintenance
Once the BW environment is implemented, tested, and delivered, we can perform the maintenance using both onsite and offsite resources. Our maintenance contracts ensure that the customer can depend on us for:
Troubleshooting and Error Correction
Creation of New Infocubes
Customization of reports
Archiving and Storage
Data Maintenance
Focus
Also Check the below Links:
Hope this helps
****Assign Points If Helpful****
Regards,
Ravikanth

Similar Messages

Roles of Implementation & Support Project of demand planner

hi to all
i let to know whats the exact job of a Planner in Implementation & Supporting project his roles and responsibility and i want to know exactly that what do he do in real time project of I & S. please answer for my query and expecting for ur response.
1) Implementation
2) Supporting
Please answer for mi query and help me in mi career further.
Thanking u all in advance .
ronald

Hi,
Demand Planners role in Implementation Project:
- Business process related requirement provide to the implementation team
- Test scenario explanation
- Unit testing as per the Demand Planner's view
- Report requirements provide to implementation team.
You will work as a Business expert or as a Core team member in the Implementation Project. Your role will be very crucial .. you will Drive the project as per the business processes of Demand planning.
Support Project :
If you are working as a Demand planner and doing day to day Demand planning work then in case any issues come you will send it to support team for correction.
You may be from Business Team work as a single point of contact from Business.
You will gather the requirement for reports/ any new devlopment and for implementation send it to support team.
In the support project you will require to see continous process improvement

Abap consultant role in implementation project

hi
may i know
abap consultant role in implementation project
and implementaion steps

SAP provides the SUIT but the service companies like IBM & Infosys do two activities to make that suit workable for a perticular client's buisness.
1. Configuration
2. Customization
The abap consultant's role is to customizing the standard suit accoring client's buisness. Also there may be many 3rd party systems involve in for the client along with SAP. To create the interface of SAP and those 3rd party systems and manage the data transfer is also a job ob ABAP consultant.

What is Developers role in Implementation project

Hi All,
Can any body tell me the Role of Developer in Implementation project
Plz reply back me to [email protected]
Regards,
Kiran

Hi kiran,
Developer will develop the objects, means If a client is located at other place senior consultrants like, functional or Techno functional consultants will gather the requirement and they will try to convert it into technical specification the the developer will start developing the objects.
Developer will do the developmnent and unit testing ..
Generally Developers will come into picture from the realization phase fo the project.
Hope iam clear.
Apparao

Internal Auditor's Role after implementation of SAP

Dear Experts,
Can you please guide me on what would be the Internal Auditor's Roles & responsibilities after implementing SAP in his organization?
Thanks & Regards,
Reshma
Edited by: Reshma Joshi on Jan 12, 2010 1:45 PM

Hi Reshma,
Whenever the Organisation is migrating to SAP, the internal auditor has to play important role. He will have to check
Whether the Trial Balance is uploaded correctly which includes
a. Uploadig of all the open items of Vendors & Customers
b. Uploading of the other Balance sheet items
c. Uploading of the P & L balances
d. Uploading of the Assets along with the acquisition cost & accumulated depreciation (asset wise) in FI & AM modules. Both should tally.
All these activities he has to monitor along with the Core Team members. Also he may play very important role during the cut-over stage also.
Also he has to ensure that whatever are the statutory audit requirements, should also be fulfilled with the help of the new system.
These are some of the important areas in which he has to pay important role. But depending on the approach of the management, this can be increased.
Regards,
Amit

ABAPer Role in Implementation Project

Hi all,
I have 3 years experience in abap module but never got oppurtunity to work in an implementaion project.Now i am looking for a job change.But in most of the job requirements i see min 1 implementation project experience required which i dont have now.In these 3 years i have worked in many abap objects and very confident in abap through self learining and support experience..now my question is what kind of exposure am missign now ? => You have missed out reading the Rules of Engagement of these forums. Please do this ASAP.
Thanks in advance...
Edited by: kishan P on Dec 30, 2010 4:57 PM

Hi marmik,
Though you ABAP skills will be of lesser use but since lot of training material is available so you will not face much problems in learning SAP GRC.
You can get lot of material including how to guides at:
https://www.sdn.sap.com/irj/sdn/bpx-grc?rid=/webcontent/uuid/00dd6b2e-57a3-2910-8a8c-e083aed57143 [original link is broken]
For istallation and configuration guides please look at foollowing link at SAP Service Market Place:SAP Software Distribution Center-> Download-> Support Packages and Patches-> Entry by Application Group-> SAP Solutions for Governance, Risk and Compliance-> SAP GRC Access Control.
For Demo of compliance calibrator :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d2f1cf9c-0d01-0010-2dac-aedd3c4f7f5b
For demo script :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5dd4ab89-0d01-0010-29a1-99e912344bf4
I hope it will be usefull for you.
Please feel free if you need more material.
Regards,
Anubha

Ejb security role & bea implementation

A role has been defined in ejb-jar as following:
<security-role>
<description><![CDATA[Deployer User]]></description>
<role-name>deployer</role-name>
</security-role>
<method-permission>
<description><![CDATA[Deployer Method Permission]]></description>
<role-name>deployer</role-name>
<method>
<description><![CDATA[All method for CCPStateBean]]></description>
<ejb-name>CCPStateBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
If the principal is included in the weblogic-ejb-jar as below, and the jndi lookup
includes the SECURITY_PRINCIPAL (e.g., jzhu), the code works fine.
<security-role-assignment>
<role-name>deployer</role-name>
<principal-name>jzhu</principal-name>
</security-role-assignment>
The problem comes when the principal is not included as above weblogic-ejb-jar
instead a role "deployer" is defined in WLS's, The user ("jzhu") is defined in
the deployer group. And the deployer group belongs to deployer role. The defaultRoleMapper
is enabled. In this scenario, the access failed due to insufficient permission.
Can ejb-jar's role relates to WLS's role. Please advise. THX.
-John

Thanks for the information. It works. I wish bea monitor this newsgroup since this
is not in their document. By the way, the following links clarifies the relationship
between DD and admin console security configuration.
http://edocs.bea.com/wls/docs70/security/cli_apps.html#1090734
-John
"Arjuna Chala" <[email protected]> wrote:
I don't know about "defaultRoleMapper", but this works
<security-role-assignment>
<role-name>deployer</role-name>
<principal-name>deployer</principal-name>
</security-role-assignment>
where <role-name> maps to a ejb-jar role and <principal-name> maps to
a
weblogic group (in this case).
"john" <[email protected]> wrote in message
news:[email protected]..
A role has been defined in ejb-jar as following:
<security-role>
<description><![CDATA[Deployer User]]></description>
<role-name>deployer</role-name>
</security-role>
<method-permission>
<description><![CDATA[Deployer Method Permission]]></description>
<role-name>deployer</role-name>
<method>
<description><![CDATA[All method for CCPStateBean]]></description>
<ejb-name>CCPStateBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
If the principal is included in the weblogic-ejb-jar as below, andthe
jndi lookup
includes the SECURITY_PRINCIPAL (e.g., jzhu), the code works fine.
<security-role-assignment>
<role-name>deployer</role-name>
<principal-name>jzhu</principal-name>
</security-role-assignment>
The problem comes when the principal is not included as aboveweblogic-ejb-jar
instead a role "deployer" is defined in WLS's, The user ("jzhu") isdefined in
the deployer group. And the deployer group belongs to deployer role.The
defaultRoleMapper
is enabled. In this scenario, the access failed due to insufficientpermission.
Can ejb-jar's role relates to WLS's role. Please advise. THX.
-John

What are the major responsibilites of abaper in implementation?

Hi gurus,
tell me abapers full role in implementation.
Thanks in advance...

Hi,
it may help u
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
Flat file can be created in your hard disk as follows:
1 Vinod Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:\FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.
with regards,
vasavi.
reward if helpful.

Indirect role assignment- PO Release strategy roles

Hello,
I am in the midst of creating PO release strategy roles for implementation and trying to figure out if indirect role assignment / position based assignment would be a good idea for these roles. The reason- there are 35 release codes.
I am pretty new at using indirect role assignment but do understand a bit about the evaluation paths. We are not implementing SAP HR so there will be no usage of infotype 105. The role will be assigned to the position and then the position to the user ID. The HR Org structure is in place (atleast for the PO release workflow).
Is this a good idea?
There is one other think that stumped me. One of the functional consultants (who is also part of business) has asked me why we can't use indirect role assignment for all function (purchasing, sales, finance etc.). For one, i know with so many users assigned to positions and then indireclty to roles, the overhead would be too much and complex and then the problem with the evaluation paths.
But i am not convinced myself that this is the best explanation to give...
Any ideas on how to put it through correctly?
Regards,
Prashant

Hi Prasanth,
I also had a similar requirement, but since there are multiple release codes, and limits, we ended up with a custom solution, since it is a bit tough when it is required to manually assign the authorization to a person who is in a seperate job role.
We have used a custom user exit, and all the values were stored in a custom table which contains Sales Organization, User, Lower limit, Upper limit, Division, and Release codes information etc.,
We have further created a custom transaction code that reads information from the table and authorizes for the upper, and lower limit of approvals along with the company code/release code authorzation checks.
Hope this helps!!
Regards,
Raghu

Activity implementer can not edit Manual activity content

user role activity implementer can not edit Manual activity content assigned to him
just he can mark complete or mark as faild
what is required to give user permission to edit Manual activity ?
Ahmed

attached user role tasks assigned, still can not edit Manual activity assigned to him
Ahmed

Java and Partner Applications - EXTREMELY URGENT

gurus,
i'm trying to register a single sign on servlet application as a partner application.
i followed ths steps as mentioned in the SSO SDK version 307 and when i try to run the application i get the following error -
******* START ERROR ********
Error oracle.security.sso.enabler.SSOEnablerException: oracle.security.sso.enabler.SSOEnablerException: java.sql.SQLException: ORA-06510: PL/SQL: unhandled user-defined exception ORA-06512: at "DVIPARTAPP.WWSEC_SSO_ENABLER_PRIVATE", line 304 ORA-06512: at line 1
********* END ERROR *********
the environment here is -
database - 8.1.7
portal - 3.0.8
os - windows NT
has anyone faced the same problem before.
any help would be greatly appreciated.
thanx a bunch.
null

Thank you very much once again for your prompt reply and suggestions. I tried the later solution using Developing Statically Protected PL/SQL (or j2ee) Applications described in Oracle® Application Server Single Sign-On Application Developer's Guide 10g (9.0.4).
Protect the servlet(or jsp) by entering the following lines in the mod_osso.conf file:
<Location /servlet>
require valid-user
authType Basic
</Location>
When this particular application added inside the portal (try to web clipp, it redirects to SSO login page.) In this case users have to login twice. Once to the default portal page, and another to this stand alone out side application. Defeats the purpose of SSO using Portal.
Your question "is it an app that you want to be able to invoke from a link within Portal?" hits the nail right on the head. The difference here is, I do not want to add as a page link, ideally I want this web application to be able to web clipped inside the portal.
Now, this is the external application (and not developed as a portlet). I have not completely understood how any web application developed as a portlet can get the user information (user/groups/roles etc) when user logs in to portal default page. And, the authorization is implemented inside this web application. They(users) do not need to authenticate once again since that is done when they login to the portal. I hope I am making sense.
I am not clear on the web application developed as a portlet. Can users, groups, and roles be implemented inside this application? If it is developed as portlet. The problem here is you have to rewrite all of your existing applications as a Portlet (either PL/SQL or J2EE). Not all applications are developed using this technology.
Your help is highly appreciated.
Very Best Regards,
-Dhiren.

How to hide the Print and Export button in analytics report or tasks pane

Hi Experts,
In BIEE 11g,
How to hide the Print and Export button in analytics report or tasks pane ?
For example:
In console,I have created one userA which is belong to BIConsumer GROUP , when I make use of the highest user 'weblogic' to create one simple report, then the userA will login the analytivs to view this report (not dashboard), it will show the print and export as below.So customers do not want to give him the privilege for printing and exporting.
In addtion, go to catalog->tasks(left corner), it will also show the print and export button. So how to hide or not access these button?
Note: Maybe it can use the policy for consumer role for implementing this requirement, but I do not know how to modify the policy. Are you facing the problem? Thanks.

Hi,
1. Create seperate folder for Reports & Dashobard.
2. For BI_Consumer (userA) set the catalog permission to view Dashboard Folder only and remove permission on the Report Folder (you can give traverse permission but don't give Open permision).
3. By this user won't be able to open or run any reports in that folder and the only way he can see the reports is through Dashboard and on dashboard the export and print buttone can be removed very easily.
Mark helpful if it helps.
Regards,
Kashi
Edited by: K N Yadav on 24 May, 2013 1:51 AM

Slow configuration changes in WebRoles and WorkerRoles - RoleEnvironment.Changing

We've been suffering for quite some time with what I think is really slow times to apply simple appsetting changes to our deployments. Let me describe our two deployments:
Deployment 1: 1 WebRole, generally two small instances. Changing an appsetting usually takes a tad under 2 minutes to complete.
Deployment 2: 1 WebRole and 3 WorkerRoles, generally two small instances for each role. Changing an appsetting usually takes just about 5 minutes to complete.
This just seems way too long. It's an appsetting after all. So today I started digging in to the RoleEnvironment.Changing event, thinking maybe my roles were being restarted for a simple appsetting change. On each of these roles I implemented a changing
event handler that looks exactly like this:
public void RoleChanging(object sender, RoleEnvironmentChangingEventArgs e)
if (e.Changes.Any(change => change is RoleEnvironmentTopologyChange))
e.Cancel = true; // restart instance on topology change
else
e.Cancel = false; // avoid restarting the instance for a setting change
Then in the OnStart() method I hook it up like so:
RoleEnvironment.Changing += RoleChanging;
After deploying old code without this to Prod slot and this new code to Staging slot and making an appsetting change on both there is essentially no difference in timing. So a few questions:
1) Have I misinterpreted how the Changing event works?
2) Is it normal to expect it to take 5 minutes for an appsetting change when I have 4 roles each with two instances? Am I fighting a battle that cannot be won?
Any insight is much appreciated...

Hi,
The code looks fine. To check whether the role still gets shutdown or not, you can handle the role's Stopping event, and write some messages to, say, table storage. Then if you see the message in table storage, it means the role has been restarted. Also please
try to write some messages in the Changing event to check whether your event handler is called.
Best Regards,
Ming Xu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Security Models 3-Tier Vs 4-Tier

Hello Security Colleagues,
We are evaluating the two models for our brand new ECC implementation.
We have license for GRC5.3,IDM 7.1.
Would you please share your thoughts/experiences ? much appreciated...
I am also searching for SAP recommendations.
Regards,

Hi Raghu,
It is the concept that is important. Typically this is used for companies with lots of org levels.
Bear in mind the following:
- You will not be able to run single role level SOD analysis using RAR (actually you will but the results will be meaningless).
- You will break the standard auth concept and every transaction addition will take more work for every addition.
- When you remove a transaction you need to evaluate all the auth objects associated with that transaction to judge if they need removing too.
- You will likely introduce additional risks if you have 1 enabler/org/value role which applies to more than 1 transaction role
- Your implementation will be harder to review/audit. This will increase your audit costs as they will likely need to perform more substantive tests as a result of not being able to check SOD so easy (you could say it is their problem, but it will also become your problem)
- As soon as the originators of the design leave then history shows that the implementation will end up a mess as staff are onboarded who do not understand this method.
- Increased support costs if outsourced.
Out of the many, many implementations I have audited, this concept has left most of them in a complete mess. I don't know if you work for an end user or a consultancy, if it is the latter then it would not be without precedent that your company is forced to pay for a rebuild one or two years after implementation. Very few have done it well.
This is just my 2p based on seeing & fixing it.
Cheers
Alex

In the Graphic Tab and Work Center Error The Page Cannot be displayed

Hi In the Solar01 and also in the Solman_Workcenter I am getting error "The Page Cannot be displayed"
In the Solar01 - I have Business Processes save and under the Graphic Tab when I am clicking on the correct Business Scenario Node. I am expected Graph to display. But Showing error
In the Solman_Workcenter - I set up the added the Starndard Role Busing Solaman Basic Role and + implementation role. When i go under Solman_workcenter transaction I am getting the same prolbem i.e "The Page Cannot be displayed"
Any Idea friends.
Appreciate your help
-Santh

Hi,
Refer note 834832. Check activation of services in transaction SICF and the patch level of your SAP GUI.
Thanks.
Kathir

Roles in implementation

Similar Messages

Maybe you are looking for