What is a "pz" process in rac?

Hi.
I have oracle cluster 10g.
I need to know what is a "pz" process. I don't know what is this and, I was finding information in metalink and the web without results.
Node 1:
oracle 10587 1 0 08:28:52 ? 2:17 ora_pz98_PROD1
oracle 9827 1 0 08:28:43 ? 3:51 ora_pz99_PROD1
Node 2:
oracle 9946 1 0 08:30:10 ? 2:12 ora_pz98_PROD2
oracle 12099 1 0 14:31:08 ? 0:00 ora_pz97_PROD2
oracle 9588 1 0 08:30:02 ? 4:09 ora_pz99_PROD2
Thanks in advance,
Milton

Milton
One PZ process for each instance is automatically started by Oracle when a query against a GV$ view is executed. AFAIK there is no way to avoid that. And I see no reason to do it either...
HTH
Chris

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

What are the oracle processes involved in Data Guard Operation

Hi All,
I have a Primary and secondary physical standby database.
I want to know what are the oracle processes involved in the synchrnization between primary and secondary.
Thanks
Santosh

The best place to get this information is Data Guard Concepts and Administration Guild
The link for 10g Release 2
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14239/concepts.htm#i1039416
The link for 10g Release 1
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10823/concepts.htm#1039415
The link for Oracle 9i
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96653/concepts.htm#1027493

What is a Business Process Repository and where do we get it in SAP?

Hi,
What is a Business Process Repository and where do we get it in SAP?

Hi,
Here is an another way to look at the BPR-Business Process Repository delivered by SAP.
1. Add the Web Dynpro application Business Process Repository (BPR) to your Favorites:
2. Choose Favorites Add Other Objects Web Dynpro Application in the SAP initial screen.
3. Enter SM_BPR_OVERVIEW in the field Web Dynpro Application.
4. Enter a description like ex. SAP BPR
5. Save your changes.
6. Now Call the saved - Web Dynpro application SM_BPR_OVERVIEW
7. You can see the BPR in a new browser window.
This info is available in SAP Help on Solution Manager.
Hope this helps.
Kathir

What's new in Process Control 2.5?

Hi,
I'm looking for information about what is new in Process Control 2.5(compare to the 2.0 version)
Thank you in advance for your help,
Regards,
Julien

The key innovation of PC 2.5 is the user experience. The highlights of this innovation are:
A new user experience based on work centers which mimics the way compliance and business users actually work
A combination of top session management and sidebar navigation leads to cleaner, more intuitive design
Broad availability of relevant contextual information as appropriate, in the form of documents and links
Pervasive search functionality, with list filtering and sorting capability to deliver information as the user needs it
Automated testing
Delivered scripts cover Financials, Procure to Pay, Sales and Distribution, and more...
Rule parameters passed to scripts extract data from the source ERP system and return evaluation results with related issues or exceptions to Process Control
Query-based scripts use SAP Query to provide additional flexibility
Use of standard SAP and customer-created reports can be returned as part of evaluation and marked as requiring review to determine whether the evaluation passed or failed
ANd much much more

Is there a way to know what report is being processed ?

In XI R2 / Webi Report Server, or XI 3.x / Webi Processing Server, is there a way to know what object is being processed ?
For example currently, I can see thru system tool like "Process Explorer" that "wireportserver.exe" has been using a lot of CPU and increasing memory for several minutes. I feel that a report is too large or complicated, but which one ?
In audit database, I can only see events like "document read", but no "begin of refresh process".
So, do I have to wait for the process to be finished to find a "document refreshed" and know what was going on ?
Moreover, at least in R2, if user cancels his refresh request (by closing his browser for example), of if request takes too much time and reaches timeout, no audit event corresponding to this refresh request will ever be recorded. In this case, I have no information at all about what report was making the report server taking so much CPU and RAM. It has just a "read" event, but so have a lot of other reports having been read during the same period of time.
Ideally, I would just have to select the latest "begin of refresh" events without "end of refresh" to know which report are currently being processed. But unfortunately the first one doesn't exist.
Has anyone an idea to get this information anyway ?
Thanks

Hello Seb
Thanks for your reply.
I was aware of this instance manager in 3.x.
In R2, I was also able to do the same with a request thru the query manager.
Unfortunately in both versions , I haven't found yet how to find informations on report being refreshed by users directly, and not by job server.
I anyone has an idea...
In R2 I have tested the -trace option of report server : it generates a big amount of lines in trace files, but that seem completely useless : no information on what report is being processed..
I don't understant why this information is so complicated to get. It could be so helpfull...
regards
François

How to map journal fields and whats is the better process type

/Journal/JournalSuspenseCostCentre     NULL
/Journal/JournalBalancingCentre     Lookup from Organisation ID
/Journal/JournalMultiCompany     u2018Nu2019
/Journal/JournalBatchNumber     NULL
/Journal/JournalNumTransactions     Total number of /Journal/JournalLine transactions
/Journal/JournalBaseDRTotal     Sum of /Journal/JournalLine/JournalLineBaseValue u2013 Debit Values only
/Journal/JournalBaseCRTotal     Sum of /Journal/JournalLine/JournalLineBaseValue u2013 Credit Values only
How to map journal fields and whats is the better process type idoc/proxies?please let me know
Journal Line
Multiple journal lines per header:
Schema Element     Data
/Journal/JournalLine/JournalLineCostCentre     Bank account control Cost Centre
/Journal/JournalLine/JournalLineAccount     Bank account control Account Code
/Journal/JournalLine/JournalLineMoneyTotal     Transaction Line Amount
/Journal/JournalLine/JournalLineVolume     NULL
/Journal/JournalLine/JournalLineDescription     Payee Name
/Journal/JournalLine/JournalLineChequeBookReference     NULL
/Journal/JournalLine/JournalLineMatchField     Cheque Number
NB Contra accounting entries should be posted to:
Schema Element     Data
/Journal/JournalLine/JournalLineCostCentre     Bank account control Cost Centre
/Journal/JournalLine/JournalLineAccount     Bank account control Account Code
/Journal/JournalLine/JournalLineMoneyTotal     Transaction Line Amount * -1
/Journal/JournalLine/JournalLineDescription     Payee Name
/Journal/JournalLine/JournalLineMatchField     Cheque Number
/Journal/JournalPeriod     Current General Ledger Period
/Journal/JournalYear     Current General Ledger Year

It looks you are new to PI,
you have to develop scenario end to end, by creating source data type and target data type(if you have XSD's not required),then use Graphical mapping (message mapping) to map source and target structures.
Search in sdn for one end to end scenario you will understand easily
Regards,
Raj

What is best word processing program for mac mini osx 10.4.11

what is best word processing program for mac mini osx 10.4.11?

Well, Text Edit is built in & free.
Lots of people like Bean or Text Wrangler...
http://www.bean-osx.com/Bean.html
http://www.barebones.com/products/textwrangler/

In Dialog server, what type of work process can I use.

Dear all,
In Dialog server, what type of work process can I use,
Can I use all types like dialog, BTC, U1 and U2 , spool, and enque
regards,
satish

Hi,
you can use dialog, BTC, U1 , U2 and spool
enque must be on only central instance becoz there is no message server on dialog instance
regards,
kaushal

What's a Business Process, really?

Hello,
in the thread BPX? A Techno functional Consultant? suggested to me her weblog <a href="/people/marilyn.pratt/blog/2006/07/27/what-is-a-business-process-really's a Business Process, Really?</a> for some clues, and added it's now <i>the time to start a thread and expand</i> about this topic.
Effectively there are some helpful definitions in the Wiki FAQ page. Nevertheless I think a discussion about the concept of Business Process is absolutely worth. So your contribution is welcome!
Cheers, Davide

a business process is a series of steps that are undertaken to achieve a goal.
Analysing BPs is like looking at a fractal. As you zoom in there is more detail that contains more processes.
eg car company
Shareholder view - build car, ship car, sell car - build car - cost? time?, ship car - cost? time?, sell car - price?
Factory forman view - materials in on time?, assemble time? six sigma?, quality check six sigma?, test passs rate?,
So a BP has a series of steps...so BPX job is to asks "can any of those steps be automated AND what's is the saving on automating the steps"
A good BPX
1. Finds the broad areas that are the biggest cost to an organisation - ie talks to some high level people looks at the accounts due dilligence type stuff...
2. Analyses processes - ie produces Visio process flows of what workers do (the skill here is getting the processes mapped out at the correct level - not to high not too low). Rate the steps in the process for variance across the organisation. How many times will this process be run...which steps require a human intelligence (ie hard to automate)...which steps can you augment/speed up with computer logic...which steps can you replace with computer logic...which steps are best left to humans...
3. Review processes with the busniess and score them in terms of greatest value.
4. Pick your SAP tool that best fits the process step and implement the process, test and roll out -
Personally I think the BPX role is not often somthing you're going to find in an individual. Small teams of 2-4 people working very closely with different skill strength areas are going to be successful in this area

What is a Business Process?

What is a Business Process?
According to me it Depends upon client Requirements. ir Inq-Qt-Order-Del-Billing.
Correct me If I am wrong.

hi
Businesss Process : any activity or event which takes under business can be termed as business process..
====
Inquiry -> Quotation ->Sales Order ->Delivery ->Invoice -> Return -> Credit memo
Transaction Codes
VA01 Create Sales/Returns Order
VA02 Change Order
VA03 Display Sales Order
VA11 Create Inquiry
VA12 Change Inquiry
VA13 Display Inquiry
VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA41 Create Contract
VA41 Change Contract
VA43 Display Contract
VF01 Create Billing Document
VF02 Change Billing Document
VF03 Display Billing Document
VF11 Cancel Billing Document
VF21 Create Invoice List
VF22 Change Invoice List
VF22 Display Invoice List
VK11 Maintain Pricing
VK15 Create Condition Records(Transaction used to enter multiple sales conditions)
VL01N Create Delivery
VL02N Change Delivery
VL03N Display Delivery
Inquiry
quotation
contrancts and Scheduling agreements
(Value contract or quantity contract)
Sales order
Delivery - Pick - pack - shipment
Post goods issue
Billing - release to accounting
[Check the document flow in table VBFA ]
Inquiry - A customers request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.
Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.
Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.
The sales area that accepts the inquiry is responsible for completing the agreement.
Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.
b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).
c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.
Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.
====
say for example below are some of the important business processes...
Free goods deetermination,
BOM processing,
Material listing and Exclusion,
Material determination,
Outline agreements,
Special sales order.
Free Goods Determination (FG)
Inclusive: - Giving a free item of same material is called inclusive.
Maintaining condition records for inclusive: -
Logistics
Sales and Distribution
Master data
Conditions
Free Goods
VBN1 Create
Enter the discount type [NA00] (Customer/Material)
Material: - enter the material, which we are giving free item.
Min quantity: - Enter the minimum quantity for which the customer how to place the order to get the free goods. [10]
From: - The free goods quantity specifies the amount for which free goods are granted in the sales documents. [10]
Unit of measure: - pc, kg, and cm.
Are free goods: - specifies how many materials we are giving as free [1]
Calculation rule: - specify pro rata basis
Free Goods: - specify [1] inclusive rebate with item generation
Exclusive: - Giving a free item of different material is called exclusive.
Maintaining condition records for exclusive: -
Logistics
Sales and Distribution
Master data
Conditions
Free Goods
VBN1 Create
Enter the discount type NA00
Select the button exclusive
Enter the material, min quantity, for, unit of measure, additional free goods.
Additional free goods: - specifies how many additional materials we are giving as free.
Calculation Rule: - pro rata 1
Additional material free good: - Specifies the other material, which we are giving as free.
M-11, 10, 10, 1, pro rata, 2, m-10 save.
Note: - In exclusive we can also enter the same material as free item.
Note: - inclusive takes 10 as 9+1 & Exclusive takes 10 as 10 + 1.
The free goods concept is based on condition technique.
SPRO
Sales and Distribution
Basic Functions
Free Goods
Condition technique for free goods
Maintain condition tables [V/N2]
Maintain Access Sequences
Maintain Condition Types
Maintain Pricing Procedures
Activate Free Goods determination [V/N6]
We need to assign the procedure to the combination of Sales Organisation, Distribution Channel, division, Document Pricing Procedure, Customer Pricing Procedure.
BOM (Bills of Material)
The item category group of a BOM item must be either ERLA /LUMF.
Defining BOM: -
Logistics
Sales and Distribution
Master Data
Products
Bills of Material
Bill of Material
Material BOM
CS01 Create.
Enter the Material
Enter the Plant
BOM usage [5] Sales and Distribution
Enter the component & 0.
In the component field enter the materials, which constitutes of the main material and enter the corresponding quantity.
For the BOM to be exploded in the sales document the following setting has to be done.
1) When the item Category group is ERLA, the item category of the BOM item is TAQ. In the definition of TAQ we need to take the value A Explodes single level BOM in the field structure scope.
2) If the item Category group is LUMF, the item category of the BOM item is TAP. In the definition of which the same above setting has to be done.
I) If the item category group is ERLA, it will bill the main item but not the components. For this the following setting has to be done.
The item category of the BOM item is TAQ, which is made relevant for pricing and item category of the components is TAE, which is relevant for pricing.
II) Item category group is LUMF bills components but not the main item. For this the following setting has to be done.
The item category of the main item is TAP, which is not relevant for pricing and item category of the components is TAN, which is relevant for pricing.
S & D, Sales, Assign item category group
Sales Doc Type Item Group USA Higher Level Item Item Category
OR ERLA -
TAQ
OR ERLA -
TAQ TAE
OR LUMF -
TAP
OR LUMF -
TAP TAN
Inter CompanyIV Sales
Material Listing and Exclusion
Material listing: - whatever the materials that are placed in listing for a customer he can access those materials only.
Maintaining Records for listing: -
Logistics
Sales and Distribution
Products
Listing / Exclusion
VB01 Create
Enter the Listing type A001and select the key combination.
Enter the customer and place the required materials in listing and save it.
Material Exclusion: -
Maintaining Records for Exclusion: -
Logistics
Sales and Distribution
Products
Listing / Exclusion
VB01 Create
Enter the exclusion type B001
Place the required materials in exclusion.
Note: - Exclusion is given preference over listing.
This concept is based on condition technique.
SPRO
Sales and Distribution
Basic Functions
Listing / Exclusion
Sl. No. Listing Exclusion
1 Customer / Material Customer / Material
2 A 1 A 2
3 A001 B001
4 A002 B002
Step 1: - Maintain condition tables for listing / Exclusion [OV06]
Step 2: - Maintain Access sequences for listing / exclusion
Step 3: - Maintain listing / exclusion types.
Step 4: - Procedures for maintaining listing / exclusion
Step 5: - Activate listing / exclusion by sales document [OV04]
Material Determination: - Substituting one product with other product is called material determination.
Maintaining the records for Material Determination: -
SPRO
Logistics
Sales and Distribution
Master data
Products
Material Determination
VB11 Create.
Enter the determination type [A001] (Material Entered).
Material Entered: - Here enter the original material which has to be substituted.
Material: - Enter the material with which we want to substitute the main material.
Reason for Substitution: - specifies the reason why the system automatically carried out material substitution.
To enter multiple materials as substitution select the icon alternative materials.
This concept is based on condition technique.
SPRO
Sales and Distribution
Basic Functions
Material Determination
Maintain prerequisites for material determination.
Create condition tables [OV16]
Maintain access sequences
Define condition types
Maintain procedure
SPRO
Sales and Distribution
Basic Functions
Material Determination
Assign procedures to sales document types [OV14]
Defining the reason for substitution: -
SPRO
Sales and Distribution
Basic Functions
Material Determination
Define substitution reasons [OVRQ]
Go to new entries and define
Substitution reason: - Specify the substitution reason [0001]
Description: - Advertising campaign
Entry: - If we check this field the system prints the name or number of the original material on the corresponding output.
Warning: - If we check this field the system displays a warning message before substituting the material.
Strategy: - Controls whether the product selection should occur automatically in the background or whether the alternative materials should be offered for a selection in dialog box.
Out come: - Controls whether the out come of product selection should replace the original entry or whether it should be recorded as a sub item of the original entry.
OUTLINE AGREEMENTS
1) Scheduling Agreements: - Its an outline agreement with the customer containing the delivery dates and the quantities. These are entered as schedule lines in the scheduling agreement.
We can create the schedule lines when we create the scheduling agreement or we can create them later.
We fulfill a scheduling agreement by creating the deliveries in the schedule as they become due.
Creating a Scheduling Agreement: -
Logistics
Sales and Distribution
Sales
Scheduling Agreement
VA31 Create
Scheduling Agreement type DS
2) Contracts: - These are the outline customer agreements that display when the materials or services are sold within a certain time period.
a) Quantity Contracts: - Its an agreement that your customer will order a certain quantity of a product from the company during a specified period.
The contract contains basic quantity and price information but does not specify delivery dates or quantities.
b) Value Contracts: - Its a contractual agreement with a customer that contains the materials or services that they may receive within a time period and Up to a target value.
A value contract can contain certain materials or a group of materials. [Assortment Module]
c) Service Contracts: - Its an agreement that contains the conditions for offering a certain service to the customer. We can manage rental and maintenance contracts in the standard R/3 system.
A service contract contains validity dates cancellation conditions price agreements and the information on the possible follow up action.
d) Master contracts: - Its a document in which we can group contracts together as lower level contracts. The master contract contains the general terms, which apply for all lower level contracts.
Creating Contracts: -
SPRO
Sales and Distribution
Sales
Contract
VA41 Create
Contract Types: -
Master ContractGK
QuantityNMS Contract
Value ContractZWK1
Value Contract GeneralWK1
WK2 Material relevant value contract
Service and MaintainSC contract
SPECIAL SALES ORDERS
Cash Sale: - Its an order type which we use, when the customer orders picks up the goods and pays for the goods immediately the delivery is processed as soon as the order has been entered and the billing is related to the order.
Creating Cash sale: -
VA01
Order type CS or BV and everything is same as sales order
Item Category BVN
Note: - In BVN the field Credit Active is not checked.
Note: - when we save the cash sale document the system will automatically create the delivery document. For this the following customizing setting has to be done.
In the definition of the document type CS we need to take the value X [Create delivery immediately if the quantity conformed for today] in the field Immediate Delivery.
Rush Order: - In the rush order transaction the goods are delivered on the same day as the order is placed.
When we save the rush order document the delivery is automatically created and billing is related to delivery.
Creating Rush Order: -
VA01
Document type RO
Item Category TAN
Note: - For the delivery to be automatically created the following setting has
to be done.
In the definition of document type RO take the value X in the field Immediate Delivery
Reward if Useful
Thanx & Regards.
Naren..

I know it is stupid but what is the word processing program on the ibook software?

I know it is stupid, but what is the word processing program installed on the ibook g4?

Hi, Wayne. Welcome to Apple Support Communities.
Is AppleWorks installed? It's what I use, and came on many iBook models.
TextEdit Is a rudimentary word processor, and is included with Mac OS X.

What type of word processing does Macbook Pro offer?

I want to switch to Mac and was wondering what type of word processing does Apple have on their MBPs'.

Hi!
This exact question was asked earlier in the week. If you do a search you can find it. The MBP comes with a trial version of iWorks Pages), and TextEdit.
http://discussions.apple.com/thread.jspa?messageID=2743826&#2743826
http://discussions.apple.com/thread.jspa?messageID=2158511&#2158511

What is the best process for conversion moving district data to city data?

Hi ALL,
I Need to write one conversion which will move the district field data into city field data in infotype 6..
It need to apply for only one Specific country which can be identified by Employee Personnel Area..and it should be apply for all active , Terminated employee as well...
What is the best process so that i can catpure all the data records of employees of the Specific country?
my approacH is..
LDB: PNP.
Start-of-selection.
RP_PROVIDE_FROM_LAST P0001 space pn-begda pn-endda.
check p0001-weks = '5200'.
rp_provide_from_last p0006 space pn-begda pn-endda.
Loop at p0006.
move p0006 to T_p0006.
if ort01 is not initial
Move P0006-ORT01 TO T_P0006-ORT02.
endif.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0006'
          subtype       = P0006-subty
   objectid      = P_record-objps
          number        = p0006-pernr     "employeenumber
          validityend   = validityend
          validitybegin = validitybegin
         record        = T_p0006.
          recordnumber = p_record-SEQNR
          operation     = 'MOD'
          nocommit      = nocommit
          dialog_mode   = '0'
        IMPORTING
          return        = return_struct
          key           = personaldatakey
        EXCEPTIONS
          OTHERS        = 0.
      Endloop.
Is this using Loop is fine? or Using PROVIDE * from p0006 between PN-BEGDA AND PN-ENDDA
ENDPROVIDE is fine?
Is my code is accurate...Bapi_employee enque bapiemployee_deque i will add apart from that is this code is fine for my requirement or any additional need to take care to capture all the employee data ?
Regards
sas

Hi,
Please use the following code: -
RP_PROVIDE_FROM_LAST P0001 space pn-begda pn-endda.
check p0001-weks = '5200'.
rp_provide_from_last p0006 space pn-begda pn-endda.
provide * from p0006 between PN-BEGDA AND PN-ENDDA
move p0006 to T_p0006.
if ort01 is not initial
Move P0006-ORT01 TO P0006-ORT02.
endif.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '0006'
subtype = P0006-subty
objectid = P_record-objps
number = p0006-pernr "employeenumber
validityend = p0006-endda
validitybegin = p0006-begda
record = p0006.
recordnumber = p0006-SEQNR
operation = 'MOD'
nocommit = nocommit
dialog_mode = '0'
tclass = 'A'
IMPORTING
return = return_struct
key = personaldatakey
EXCEPTIONS
OTHERS = 0.
endprovide.
Hope this will help you.
Thanks & Regards,
Gaurav

What is the Successfull processed IDOC status number?

Hi Experts
What is the Successfull processed IDOC status number?
arjent Please.
Thanks in advance
Sekhar

Hi Chandra,
Below are IDoc Process Codes
For outboud Idocs:
1 IDoc created
2 Error passing data to port
3 Data passed to port OK
4 Error within control information of EDI subsystem
5 Error during translation
6 Translation OK
7 Error during syntax check
8 Syntax check OK
9 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the receiving system (ALE service)
40 Application document not created in receiving system
41 Application document created in receiving system
42 IDoc was created by test transaction
50 IDoc added
For Inound Idocs
51 Error: Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc-Copy from an R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
Regards,
Satish

What is a "pz" process in rac?

Similar Messages

Maybe you are looking for