MRS- Transfer assignment status from MRS to PS

Hi Experts,
The business scenario is that when the assignment is created for a network activity in MRSS, we would like to set the user status in network header or activity.
Is there any standard way to setting the status in network?
My another question is that, is it possible to manually set the status in assignment in MRSS? if yes, how can this be done?
Thanks in advance.
Regards
Manoj

There is also an option in the customizing to exlude orders based on the order header user status. This can be found under Sources of demand -> Orders -> Define resource planning relevance for PM/CS orders.
A user status has to be added and linked to TECO, then 'Relevance' checkbox has to be unmarked for the corresponding user status.
THe only problem is that MRS (MRSS/PLBOTIME) will display orders with assignments anyway.
We are now looking for a way to (automatically) remove the assignments from MRS when an order is TECO'd to prevent the orders from appearing.
Does anyone know how to achieve this?
Thanks.
Jasper

Similar Messages

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

Unable to transfer Purchase Requisition from ECC to EBP

Dear Friends.
We are unable to transfer PR from ECC to EBP. System issue stop message in SLG1 transaction for object BBP_EXTREQ
Stop Message Type: Document type for determined backend system is missing.
Warning Message Type: Grant 1111 does not exist.
As per configuration guide we have performed following setting in EBP client
1. We have created organization unit Entry Channel under company code.
2. Under Entry Channel we create Local Purchasing Organization.
3. Under Loc Purchasing Org we created Local Purchasing Group with
 - attribute BUK as backend company code
 - attribute BSA as backend PR type (NB)
 - this group is responsible for Entry channel procurement (setting in Function tab)
4. Under Loc Purchasing Group we assigned RFC user which is same defined as RFC user in both EBP and ECC client.
 - attribute DP_PROC_TY defined as backend ECC PO type (NB)
5. Attribute CUR define for entry Channel.
6. Remote connection established with the same user defined under Organization Unit
7. Remote user has profile sap_all and sap_new authorization.
8. Material group, Material Type and Vendors are replicated from backend system.
9. Sourcing always allowed is set for all product categories in Define sourcing for Product Category.
10. Extended Classic Scenario is active.
11. Defined Tolerance check and assigned TOG attribute.
Performed following setting in ECC client.
12. Defined RFC connection and user same as defined in Organization unit.
13. Defined profile which reference to EBP logical system
14. Maintained table V_T160EX with Material group/Pur group/ Profile combination.
Finally transfer Purchase Requisition from ECC to EBP via report BBP_EXTREQ_TRANSFER. Further the outbound Queue fails with status ANORETRY. Also the log displayed the error Application aborted due to serious problems
SLG1 in EBP issues stop message Document type for determined backend system missing and warning message Grant 1111 does not exist.
Any idea what could be the reason?
Please help!!
Sandeep

Hi
It seems there is some problem with the Configuaration settings in SRM as well as R/3 side.
Anyways, please have a look at the following links, which might help.
Direct Procurement
http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm
Prerequisites for External Requirements
http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
Attributes for the SRM Scenario
http://help.sap.com/saphelp_srm50/helpdata/en/84/a7e3389870c05ce10000000a114084/frameset.htm
Direct Material Scenario: Other Planned External Requirements
http://help.sap.com/saphelp_srm50/helpdata/en/6a/4b9e3b891da20ee10000000a114084/frameset.htm
Number range settings
http://help.sap.com/saphelp_srm50/helpdata/en/5d/fd7d3cb7f58910e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm
Define Transaction types
http://help.sap.com/saphelp_srm50/helpdata/en/10/fd7d3cb7f58910e10000000a114084/frameset.htm
Direct Material Scenario with Planning in SAP APO
http://help.sap.com/saphelp_srm50/helpdata/en/d3/4b9c3b122efc6ee10000000a114084/frameset.htm
Hope this will help.
Regards
- Atul

How to transfer vendor master from MM to SUS?

Hi friends
How to transfer vendor master from MM to SUS
Are the following steps correct
1.create vendor master in MM
2.use tcode BD14 in MM and enter partner system as SUS ( to send vendor master)
3.use BD15 in SRM to accept the master data from MM.
Please let me know if i am wrong
Thanks
Vinny

Hi Vinny,
Please follow below steps for transferring vendor master from MM to SUS.
!) Create a vendor master in MM and assign class type ALV under enviornment-Classification tab.
2)Go to BD14 and enter following fileds
Vendor number
Class
Message type
Target System...
Before doing BD14 hope you have done all the partner profile configuraion as well as model view creation and mapping has been established between MM to XI to SUS.
Before repliating vendor, please note that vendor root org unit has been created in SUS system.
After executing BD14 then check in your mm system WE05 whether idoc has been generated and sent to XI system.
If sent to XI system successfully then please check in SXMB_MONI t-code in XI what is status then finally check in SUS.....
If useful points please...
Thanks
Ravi

Shipping and delivery status from R/3 to CRM

Hi all,
we are creating sales orders in CRM and replicating it to R/3. CRM is the owner of the document.
Now whenever changes are done to sales order in CRM, the changes are replicated to R/3.
Let's say the shipping status is updated in R/3. Now the requirement is the changes need to be replicated
back to CRM.
I can use the scenario X + Y or X alone. But with X or X + y scenario Once I make changes in R/3 then the
document owner changes to R/3. this means any further changes in CRM will not be replicated back to R/3.
I require all changes from CRM to be replicated to R/3, but from R/3 I require the shipping and delivery status to be replicated back to CRM. How could this be achieved.
It would be great if you could share the experiences.
Thanks
Jothi.

Hi all,
I have a similar requirement. Can you please tell me how to go with it?
The requirement is to send the user status from CRM (where the request is generated) to R3 (where the material is processed).
The user status of the return order in CRM should be sent real-time to R3. Any updates to the user status in CRM should result in a corresponding change in the user status in R3. Any updates to the user status in R3 should trigger a corresponding change to the user status in CRM. All user statuses must be available in BI/BW for reporting and analytical requirements.
From R3 to CRM Standard R3-CRM middleware exchanges information between the two systems any time a transaction is created or changed. At this point the order information is exchanged between the two systems depending on whether the item or the header level data is changed in R3. The development should be able to download the user status at the header & the line item level when the middleware brings down R3 sales transaction data to CRM. For the sake of simplicity the status profile in R3 and CRM will be defined exactly the same therefore we do not need a mapping table between the two systems. This information should also be exchanged in case the line item is deleted / cancelled / rejected.
The same from CRM to R/3.
Processing restrictions :
This should not be transaction, item category or status profile specific so that as and when a new transaction type, item category or a status profile is added it should still be allowed to transfer between the two systems.
Should be developed as an enhancement to the standard middleware data stream between R3 and CRM.
Regards,
Raju

LabVIEW DSC: How to get alarm status from the area?

Colleagues,
I have, lets say, 50 Shared Variables where alarming enabled. Some of these variables assigned to area, so I can get status of the entire area or acknowledge an entire area of alarms (prior to version 8.x there was groups of the tags).
Now I would like to get alarm status from the entire area. How can I do it?
In version 6 I was able to wire tag group to Get Alarm Summary Status. Now, in version 8, Alarm Status.vi can be wired to the array of the variables, but not to area. Is it possible to get all variables from the area?
regards,
Andrey.

I am not sure if I should be posting my problem under this particular topic. I am having trouble understanding acknowledge alarm vi and what this vi is supposed to do is not clear to me yet.
I have around 300 shared variables in my project and I have created a particular vi just to view the alarms that may pop up during runs. I created a main menu and this alarm vi can be accessed upon a button click in the main menu. Users get alarm alert based on sound configuration. Then he can navigate to the alarm vi and acknowledge the alarm. The alarm vi only contains alarm and event display found under DSC module.
The problem is everytime I click the alarm button in the main menu, it takes around 2 minutes for the alarm vi to update which is very annoying and unsatisfactory in the middle of run. I am not sure why it happens and I haven't got any response from support yet. These shared variables are managed under 10 different library files that are set up based on different loops of the process (flow, pressure and so on).
Then I looked into three alarm examples that ship with DSC module. None of these examples use acknowledge alarm vi. I implemented another vi similar to alarm demo vi in that example - containing multicolumn listbox. I created acknowledge event containing acknowledge button and used the acknowledge alarm vi under this event. Read vi alarm is under timeout event.
When I click the acknowledge button as soon as I see the alarm in multicolumn listbox, nothing happens - the color of font does not get changed to purple neither any alarms get acknowledged. I tried to aknowledge alarm by variable name or alarms or alarm area, it does not give me anything. What is this acknowledge alarm supposed to do? I tried to find examples everywhere in the web that uses this particular vi and haven't found one yet.

Transfer of material from sales order stock to subcontractor

Iam having subcontracting operation in routing. But i am not able to transfer of material from sales order stock to subcontractor when i do 541 movement

Dear Mayuresh,
You cannot move Sales Order assigned material directly to Sub contracting Vendor stock.
For doing so firstly unassign the Sales order stock by transaction MB1B & movement type 411E.
After this you can provide the stock to the vendor by transaction MB1B & movement type 541O.
Other way is to create account assigned Purchase Orders. Thereafter create virtual sub contractor storage location in your plant. Transfer your Sales Order assigned material to these Virtual locations so that you can see the stock provided to the vendor. Now during Goods Receipt of the finished goods you can consume the material by movement type 543E.
Regards,
Subha.

How can I transfer my photobooks from iphoto 08 on osx 10.5.8 to iphoto 11 on macbook osx 10.8.1 without loosing layout?

How can I transfer my photobooks from iphoto 08 on osx 10.5.8 to iphoto 11 on macbook osx 10.8.1 without loosing layout? I prepared 3 books in iphoto 08 and wanted to order them yesterday. I got the message, that this version is not supported anymore. I also have a macbook osx 10.8.1. However I did not manage to transfer the books to it. What can I do? I really would not like to recreate the books from scratch in th new version.

You will have to convert your 08 library to iPhoto 11 by copying the library to your Macbook and opening it with iPhoto 11.
However, check to see if the theme you're using in 08 is available in 11. If it isn't you'll probably lose the book or be assigned to some other theme.
If the theme you've chosen isn't available in 11 find one that is available in both versions and convert to it in the 08 library before you move it to 11.
OT

Transfer of values from one recon to other recon account

Guru's,
I wanted to change the recon account of a vendor from 8050001 to 8050002.
Few entries are already posted in the vendor with the recon 8050001. I know that FAGL101 can be used to transfer the values from 8050001 to 8050002.
In the OBBW I did the configuration like this
Reconciliation account : 8050001
Adjustment Account : 9000014(Clearing account)
Please advise me if I need to do any other settings in Config and also tell me the procedure to run that in FAGL101.
Thanks in advance and points will defnitely be assigned.
Deepak

Hi,
I dont think you can update members. However, you can definitely send transactional data from one application to another using the DESTINATION_APP statement.
You have a good example available in BPC 320 on beforerange and afterrange.
Lets say that there are 5 columns in the report after the EVDRE expansion is done. Then in the beforerange or afterrange, you can use EVRNG function with a range of 5 cells. Lets say that you define EVRNG(J1:N1). In these cells, you can use formulas like EVSUM etc, and these formulas will be taken by the rows in your EVDRE report. If you define afterrange, then you will have additional row at the bottom. If you define beforerange, then you will have additional row at the top.
Hope this helps.

Transfer of hours from CATS to HR

Hi.
One of my customers has set up a transferral of hours from CATS to HR (IT2001 and IT2002) with help of trx CATA.
The process includes approval of hours via CATS_APPR_LITE which slows everything down considerable. In the time gap between recording of hours, and approval of hours, WBS-elements are closed. This causes error messages in program RCATSTAL (trx CATA).
Does any of you have any suggestions of how to make the process smoother?
I've been thinking of direct transfer to HR - either from CATS or from CATS_APPR_LITE. If the direct transfer is triggered from CATS, how can the hours then be approved?
Thank you in advance!
Odd

Hi,
You can do one thing than. Use SAP standard task for approval process.
For more details refer the below links:-
1. http://help.sap.com/erp2005_ehp_05/helpdata/EN/64/4003fb470211d189720000e8322d00/content.htm
2. http://help.sap.com/erp2005_ehp_05/helpdata/EN/3e/697b423737dc54e10000000a155106/content.htm
Thanks & Regards, Swapnil Mishra
Hi again, Swapnil.
Thank you for your effort in helping me solve this. One way of speeding up the approval process would be to transfer given A/A codes without approval, and only have some A/A-codes through the apporval process.
As I can see from your refered links, hours HAS to be approved (status 30) before they can be transfered to HR.

Change status from active to inactive

Hi Experts,
How can I change status from active to inactive for the InfoCube?
Thank you

You can deactivate a cube by deactivating one of the infoobject in it:
select one of the char in the cube
menu option Extras/Unlock infoobjects
The system will offer you to delete the cube content.
If you agreed, the cube becomes inactive.
Please assign if helpful

Removing assigned budget from commitment item.

Hi.
I am facing a problem with how to restructure commitment item in our R3 system. The problem is that when the commitment item has been created in our system, person responsible chose "Not Directly Postable" option though it should have been "Directly Postable". Right after that budget has been assigned to this commitment item. I went through a number of FM documents and they all say that feature "postable"/"not postable" is not changeable to begin with and on the top of that commitment item cannot be changed once it has any kind of budget assigned to it. As I understand I need to roll back assigned budget (thank God, nothing else has been done), then delete this commitment item, then create it again. I couldn't find anything that explains how to do that. There is a Tcode FMDOCREV but it reverses the whole document and this is not an option for us as by the same document budgets have been assigned to a number of commitment items and spent from them already.
To summarize my post: I need to remove assigned budget for my commitment item (the rest seems to be easy).
Please, advise.
Thank you.
Regards,
Nazim

Hi,
Maybe you can use this work around solution:
1. create a direct postable and budgetable CI
2. in BCS derivation tool, replace the old CI with the new CI when applicable
3. in FMDERIVE, add the new CI to the applicable derivation rules
4. transfer the budget from the old CI to the new CI using FMBB.
If your FM master data is year-dependent, you have the option of use back the old CI by checking the postable indicatior for the new FY.
Regards,
Ming

Can we setup the transfer of 'objectives' from one appraisal to another?

Dear All,
Is it possible to setup a policy to transfer the 'objectives' from one previously started/done appraisal to another newly created appraisal automatically on the creation, based on some criteria like following:
- Transfer all non-achieved objectives from a closed 'annual appraisal' (for year 2011) ..INTO.. next year's (for 2012) annual appraisal.
- Transfer all achieved objectives from all closed 'assignment/engagement appraisal' between 1st Jan to 30th Jun ..INTO.. an 'interim appraisal' for the period of 1st Jan to 30th Jun (for the same year)
- Transfer all achieved objectives from all closed 'assignment/engagement appraisal' between 1st Jan to 31st Dec ..INTO.. an 'annual appraisal' for the period of 1st Jan to 31st Dec (for the same year)
- Transfer all achieved objectives from all closed 'interim appraisals' for the period of 1st Jan to 30th Jun ..INTO.. an 'annual appraisal' for the period of 1st Jan to 31st Dec (for the same year)
If it is possible.....what is the detailed method to do that? ....In my opinion it can only be done via customization....am i right?
Regards,
Talha.

Hi,
Unfortunately such functionality does not exist. If you are using PMP, you will be able to do this to an extent but not the way you want based on certain criteria.
Regards,
Vinayaka

Transfer of Stock from Warehouse to Warehouse

Hi ,
I have the following query.
Warehouse 1 is assigned to Plant 100 and Storage location 10.
But now the client wants to assign Warehouse 2 to Plant 100 and Storage location 10.
As per the requirement I changed the assignment. But now I have come to know that there is stock for certain materials in Warehouse 1. Since the assignment is already done, how can I move the stock from Warehouse 1 to Warehouse 2
Appreciate the help.
Regards
Mohan

"But lets say I assign Warehouse 1 back to Plant 100 and storage location 20"
I presume by storage location 20 you mean 10
Yes I believe this will work.
1) Assign back W/H1 to 100 / 10
2) Check if there is any stock inconsistency. Whatever stock available in W/H-1 for pl / st locn 100 / 10 should match stock at IM level.
3) Create new st locn 20 (in your last message it is 30) under pl 100 and assign W/H-1 to 100 / 20
4) Transfer all stk in W/H-1 from 100 / 10 to 100 / 20. At the end of activity there should be no stk at st locn 10 and no stk in W/H-1 for pl / st locn 100 / 10. All stock in W/H-1 will be for 100 / 20.
5) Now remove assignment of W/H-1 from 100 / 10 and assign W/H-2 to it.
6) Transfer all stk from 100 / 20 to 100 / 10 back.
At the end of activity stock will be in W/H-2 with pl / st locn 100 / 10.
Reg,
Sudhir

Transfer executable report from one server to another

hi all,
How to transfer executable report from one server to another?
please reply fast
its urgent
thnx in advance

Kush,
To transfer a object from one server to another server it should be assigned to a package ie Dev Class so that a transport request can be created.Once the request is created we will release it using SE09 and then ask the basis consultant to move the request from Dev to Quality and then Dev to Production.
$TMP objects are called as local objects and can't be transported.
K.Kiran.

MRS- Transfer assignment status from MRS to PS

Similar Messages

Maybe you are looking for