Promotion in approval process don't close data at owner.

Hello!
I have a problem in approval process in planning unit hierarchy. I created planning unit hierarchy. When I run approval process, ownership of the process moves to user, which specified in planning unit hierarchy as "Owner". When owner promote approval process to the next user "Viewer" and current position is at "Viewer" tha data couldn't be entered by Owner. But in my situation data don't close to enter at Owner, and he can change the data, which he sent to Viewer. It isn't correct. Why data don't close to enter at Owner, though the current position of approval process at "Viewer"?

From what I have been reading from other posts on this forum, the issue may
be caused by the clear history settings.
Press the '''<Alt>''' or '''<F10>''' key to bring up the tool bar.
Then '''Tools > Options > Privacy'''.
The button next to '''History''', select '''Use Custom Settings'''.
At the bottom of the page, turn on '''Clear History When Firefox Closes.'''
At the far right, press the '''Settings''' button. Turn on ONLY '''Cache''' and
'''Form And Search History''' leaving the others off.
This is not a cure but will make it easier if Firefox locks up.
'''https://support.mozilla.org/questions/997866?esab=a&s=&r=1&as=s''' {web link}

Similar Messages

Vendor Approval Process

Dear Experts,
I have a requriement from our company, that when opening vendor code, we want multiple release prococedure, means first sourcing team approve the vendor in system , then QA Team approve the vendor, then Supply chain team approve the vendor in the sytem, then finally the vendor should be approved by CEO. Then vendor is treated as active in sap.
How to achieve this, I have not seen such release procdeure for vendor, please suggest me some workaround, if there is no direct procedure.
My requirement is urgent.
Regards
Ishu

Hi,
This is something not in standard SAP. The approval process of the vendor should be done internally by the management and not supported in SAP. There is only a transaction to create vendors either XK01, MK01 or FK01 all of which are single transactions. The person who creates vendor in your company can be restricted to use the tcode unless the internal approval process done by the management to create the vendor.
Other way is you can think of blocking the vendor which you donot want to use in the procurement activities, this will restrict unwanted vendors entering into the system even by accident.
Regards
Shiva

Approval process for Personal Data Change in ESS

Hi Experts,
We need to implement approval process from Manager whenever the employee changes his Personal Data through EP in ESS.
Is there any standard method or process for doing that. Or any way of doing it without customization.
Thanks
Ash

Hi,
Do the Admin Personalizations in Portal, follow the note
1234273 and do the Personalization accordingly.
Hope this helps.
Cheers-
Pramod

Workflow Approval Process: 1)How to insert Custom Data into Windows Workflow database? 2)In workflow Approval Process while creating new request ,how to insert our custom data like approvers ,requester,object info into WF DB?

hi ,
here the description about my question.
1)i am working on windows workflow,we need to implement approval process for my project.
2)we have multiple approvers for one request,requester,created object information.
3)now i want to insert and retrieve, created instance information from windows workflow
database.with all following details
i)Workflow instaceId,
ii)current state of work flow(idle,complete,pending)
iii)approvers information.
iv)requester information.
v)created object information.
here some of the links, which i am trying for solution:
https://wf.codeplex.com/wikipage?title=Tracking%20states%20with%20WorkflowApplication[^]
https://msdn.microsoft.com/en-us/library/ee622977(v=vs.110).aspx[^]
please answer to my question. if you want to send any examples send me to my email address.
[email protected]

Hi，
According to your description, it seems that your main issue is about customID paramerter in workflow approval prcess.
About this, please refer to the two samples:
http://blog.petegoo.com/2010/08/22/workflow-4-email-approval-sample/
http://cgeers.com/2010/04/10/windows-workflow-in-asp-net/
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.

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
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.
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.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Approver Details Not Visible After Changing the Approval Process

Hi Gurus,
This expense report belongs to an open approval task when an approval process has ended its validity date.
After a new approval process is activated, all pending approval tasks experience the issue of approver details not showing.
In order to reproduce following steps need to be done :
1. Deactivate the current approval process and activate the new approval process.
2. When the status of the recently deactivated approval process is "Ended With Open Tasks", go to the "Show Open Approval Tasks" to
see the open approval tasks.
3 Check the Cost Assignment area for expense report which is in the open approval tasks.
3. Approver Details are available.
4. The approver sees the expense report on his/her approval list.
Once the approver approves, it doesn't go out of his/her approval list and the expense report is still pending for approval.
To determine if the expense report has no other pending approval from anyone else, there should be the approver
details but the issue is it doesn't show up.
The expense report is also stuck on the approver's approval list even after approving.
Workaround provided to the Customer: Recall the ER and submit again for approval.
But as per customer there should be a background job to refresh the expense report to reflect the approval details.
And issue should not occur as explained on the point 4.
Kindly suggest if anything is possible to improve the system behavior.
Regards,
Rahul Mishra

Hi Rahul,
Although we have a workaround, I believe a permanent solution has to be implemented.
In cases when an expense report has more than one approver (for example there are 4 approvers) and the 3 approvers had already approved, I think it will not be good to recall the expense report and resubmit because the traveler will have to seek for approval again from all the approvers.
Regards,
Catherine Mapili

Approval Process doesn't work correctly

Hi,
I developed custom request template for self-request provisioning for resource with child table data. Also I deployed custom Request Dataset only with child attribute field definition for this resource:
<request-data-set
xmlns = "http://www.oracle.com/schema/oim/request"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation = "http://www.oracle.com/schema/oim/request"
name = "ProvisionResourceHP"
entity = "HP"
operation = "PROVISION">
<AttributeReference
available-in-bulk = "true"
length = "100"
widget = "text"
type = "String"
attr-ref = "UD_HP_ROLES"
name = "Roles">
     <AttributeReference
     lookup-code = "Lookup.HP.AppRoleList"
available-in-bulk = "true"
required = "false"
     length = "100"
widget = "lookup"
     type = "String"
     attr-ref = "AppRole"
     name = "AppRole"
          primary="true"/>
</AttributeReference>
</request-data-set>
When this request approved by all participants of the approval process, Resource do not in provisioned status! In the resource history only - System Validation status Pending!!!

I resolved this issue but not complitly. I checked Auto Save Form check box on Process Form and its worked.
But I do not need Auto Save, because on child table attrubute i don't have any prepop adapter so it always been unpopulated during direct provisioning....
How to solve this new issue???

Provision for Approval process

Dear Experts,
I have a requirement "To be able to provision for Approval process by FInance, when role of business partner upgraded from prospect to customer"
I guess this is done through Workflow concept. but I don't have Idea in detail.
Looking forward for reply
Regards
Manu

About your questions...
1. According to my knowleadge there is no such standard functonality. But I implemented something similar in our company in the folowing way:
- prospect is created in CRM
- when prospect needs to be transformed to customer, salesman issues task with filled questionary
- finance departments receives this task and if it agrees transforms frospect to customer in ERP with VA07
2. If you mean that only certain data should be maintained by certain companies, then only via coding this could be achieved.
3. If you mean that in relatonship you define, to which organization contat person belongs, then I'm not sure. Never tried it. For employees I know it is possible so robably it could be done also for contact persons.
4. You can store documents. But if you want to have special access to this documents, then this would not be the case.
5. Yes. You can use account hierarchies for that.
Regards.

Approval Process in Cloud

Hello all,
I have configured the approval process according to the SAP Cloud Applications Studio guide.
1) First user creates the Price Request and submits for Approval
Second user sees the notifications and task on top of the Custom BO.
When the approval clicks on the messages, it prompts that "You do not have sufficient authorization to execute this task"
Also in the Managing My Area work centre, there are 0 task and 0 notifications.
1) What is the authorization issue?
2) How to get the tasks and notifications to show up in Managing My Area?
Thank you!

Hi,
Yes this is possible in VC but I guess we don't have a ready document on sdn which could guide you. Ask your ABAPers to write BAPIs for approval/rejection of invoices/POs/PREQs.... Once done, you need to call those data services in VC and pass relevant parameters to it.
Regards,
Murtuza

Approval process in vc

Hi
I want to do approval process in vc.is it possible. pls refer any document to do this.
Rgds
Patrick

Hi,
Yes this is possible in VC but I guess we don't have a ready document on sdn which could guide you. Ask your ABAPers to write BAPIs for approval/rejection of invoices/POs/PREQs.... Once done, you need to call those data services in VC and pass relevant parameters to it.
Regards,
Murtuza

Can a Approval process manually invoked from a jsp!!!

Hi everyone,
I have attached new jsp to the left menu of xelsysadm. In this jsp user will fill up information. on submit i should invoke an approval process once its approved i will make changes on Target system.
Can this be done through API. What would be the approach!!
Thanks,
murli

Here is a sample to create a request
     public long createResourceRequestForUser(String resourceName, String userId, boolean addResource)throws OIMServiceException
          logger.debug("Entering createResourceRequestForUser") ;
          long reqKey=-1, usrKey=-1, objKey=-1;
          tcUserOperationsIntf oimUserUtility = null ;
          tcRequestOperationsIntf oimRequestUtility = null;
          tcObjectOperationsIntf oimObjectUtility = null;
          try {
               oimUserUtility = (tcUserOperationsIntf) oimUtilityFactory.getUtility
                                                       ("Thor.API.Operations.tcUserOperationsIntf");
               usrKey = getUserKeyByUserId(userId, oimUserUtility);
               oimObjectUtility = (tcObjectOperationsIntf) oimUtilityFactory.getUtility
                                                       (Thor.API.Operations.tcObjectOperationsIntf");
               Hashtable objHash = new Hashtable();
               objHash.put("Objects.Name", resourceName);
               tcResultSet objSet = oimObjectUtility.findObjects(objHash);
               objKey = objSet.getLongValue("Objects.Key");
               logger.info("Object Key for the resource " + resourceName +" is " + objKey) ;
               oimRequestUtility = (tcRequestOperationsIntf) oimUtilityFactory.getUtility
                                                       (Thor.API.Operations.tcRequestOperationsIntf");
               HashMap reqMap = new HashMap();
               reqMap.put("Requests.Target Type", "U");
               reqMap.put("Requests.Type", "U");
               //Check whether the resource is for revoke or grant for the service
               if(addResource==true)
                    reqMap.put("Requests.Object Request Type", "Add");
                    logger.info("Creating request to provision resource "+ resourceName + " for user "+ userId) ;
               else
                    reqMap.put("Requests.Object Request Type", "Revoke");
                    logger.info("Creating request to revoke resource "+ resourceName + " for user "+ userId) ;
               //Create the request
               reqKey = oimRequestUtility.createRequest(reqMap);
               logger.info("New request created with request id "+reqKey) ;
               //Adding user to be provisioned for resource object
               oimRequestUtility.addRequestUser(reqKey, usrKey);
               logger.info("Adding user for which the resource is to be provisioned or revoked") ;
               //Adding Object to be provisioned
               oimRequestUtility.addRequestObject(reqKey, objKey, false);
               logger.info("Adding Object to be provisioned or revoked ") ;
               oimRequestUtility.completeRequestCreation(reqKey);
               logger.info("Completed and submitted the request ") ;
          }catch(Exception e)
               tcae.printStackTrace();
               logger.error("Error in resource request for the user "+userId + " :"+e.getMessage()) ;
               throw new OIMServiceException(tcae.getErrorCode() + ":" + e.getMessage()) ;
          } finally {
               if(oimUserUtility != null){
                    oimUserUtility.close() ;
               if(oimObjectUtility != null){
                    oimObjectUtility.close() ;
               if(oimRequestUtility != null){
                    oimRequestUtility.close() ;
          logger.debug("Leaving createResourceRequestForUser") ;
          return reqKey;
     }

Workflow - Timesheet Approval Process

Hello,
I am brand new to workflow. At my client a Manager is responsible for approving his/her subordinates' timesheets.
However - if that Manager is absent, they want the Manager's Supervisor to be able to view and perform the approvals for all of his subordinate's (Manager's) personnel.
I'm not sure where to even begin. I believe I should create a new View in the IMG - for an evaluation path (would the S-S standard SAP evaluation path be appropriate)? I do not know how the evaluation path, view, and Supervisor : Manager Business Workplace will enable what the client is asking. Will simply creating the view enable this??
Really appreciate any advice and direction.
Dave

1 and 2) Are you sure that IDOCPACKET and ATTENDENCE have anything to do with CATS? I don't believe so. The time stamps of these events most probably don't event match with your CATS release and/or approval.
If you need to set up some kind of approval process workflow, if I remember correctly it is configured here: SPRO > Cross Application Components > Time Sheet > Specific setting for CATS Regular > CATS Regular > Set up data entry profile.
Regards,
Karri

TimeSheet Approval Process workflow

Hi All,
Please let me know how time sheet standard behavior of approval workflow.
I ran the timesheet approval process, I found in the event trace, the following business objects are showing for the process.
When employee requests for a timesheet approval, there is no workflow triggered ( no receiver in the SWEL), it is showing BO IDOCPACKET and event MASSINPUTFINISHED and when approval approves the request it is triggered the workflow (receiver is WORKITEM) single step type.
Please clarify me on
1. Why IDOCPACKET is triggered?
2. Why ATTENDENCE is triggered?
3. whenever a time sheet request is created by user, approver will get notifications, where these configurations have been maintained?
4. When approver approves/rejects the request, initiator will get the notifications, where these configurations have been maintained?
Thank You in advance.
Regards,
Pavan.

1 and 2) Are you sure that IDOCPACKET and ATTENDENCE have anything to do with CATS? I don't believe so. The time stamps of these events most probably don't event match with your CATS release and/or approval.
If you need to set up some kind of approval process workflow, if I remember correctly it is configured here: SPRO > Cross Application Components > Time Sheet > Specific setting for CATS Regular > CATS Regular > Set up data entry profile.
Regards,
Karri

Create Material directly in active area without approval process ( Bypasing Staging)

Hi Experts ,
I have one requirement where Material need to be created directly in active area with out any approval process.
So I need to bypass staging area data store.
Please give your valuable input to achieve that.
Thanks in advance.
Regards,
Samrat

Hello,
From the discussion above, I can understand this is a requirement. However, I would like to understand the reasoning behind this requirement. The whole point behind MDG is to avoid direct creation of master data and instead "govern" the process first. If you are going to create material, then use MM01 directly as Sanjay suggested.
If you are looking for a web-based UI, you are better off looking for a standard Web Dynpro application (or create your own) instead of mis-using the MDG application.
In any case, you can't completely by-pass the staging area. However, you can configure a single-step rule-based workflow such that the material goes into "activation" immediately. Keep in mind that the material will not be available immediately, but will take a few minutes depending on your system configuration until the material is activated completely in the system. Error handling, etc. will need to be done on the MDG layer which could prove to be an unnecessary burden should you decide to go this route.

I get an error message saying "system overload, the audio engine was not able to process all the required data in time (10011)

i get an error message saying "system overload, the audio engine was not able to process all the required data in time (10011)

The thing is, that error message has been appearing when playing/recording a track that was running perfectly a few minutes ago and nothing has changed!
That can mean, that your project is too ambitious for your Mac. Are you using many complicated automations on that track?
4GB memory is not much, when doing audio processing. GarageBand will need all memory it can get, or will be forced to continually swap pages to your disk, to free RAM, and that can cause this error.
When this error occurs, it is best to restart the computer. This will free your RAM. Close all other applications that are competing for memory, i.e. other multimedia applications, and Safari.
Also, make sure, that you have plenty of free disk space. Don't let the free disk space drop below 20G.
Where is your project located? On an external drive or your internal drive? If it is on an external drive, connect this drive directly, not daisy-chained, or move the project to your internal drive.
I got up to eat, came back and tried to continue but GarageBand shuts down and displays that message every time I try to run the song. I've also recently run songs with several more tracks than this one and they worked perfectly. Any tips?
Are your other projects, that worked perfectly, still working?

Promotion in approval process don't close data at owner.

Similar Messages

Maybe you are looking for