SD PROCESS FLOW PPT

Pls can any one share process flow ppt documents (SD)

hi
Inquiry: Once we receive the quotation from the customer then as a vendor we need to check whether we can deliver the goods with customer conditions or not.
Quotation: Once we finish the inquiry then as a vendor we need to send quotation to the particular customer.
Sales Order: Once we receive the purchase order from customer then as a vendor we need to raise the sales order, while raising sales order we should know the partner functions.
Sold-To-Party – who as raised the purchase order.
Ship-To-Party – where we need to deliver the goods.
Bill-to-party – to whom we have to give the bill.
Payer – who is going to pay the money?
Goods Delivery: After raising the sales order as a vendor we need to deliver the goods.
Billing: While delivering the goods we need to send the billing document.
Finance: Once we deliver the goods with billing vendor finance guy will interact with the customer finance guy for finance settlements.
Transaction Codes:
Inquiry – VA11
Quotation – VA21
Sales Order – VA01
Goods Delivery – VL01N
Billing – VF01
Commonly used SAP SD tables:
Sales Documents:
VBAK – Sales Document: Header Data
VBAP -Sales Document: Item Data
VBUP – Item Status
VBUK – Header Status and Administrative Data
VBFA – Sales Document Flow
Delivery Tables:
LIKP – SD Document: Delivery Header Data
LIPS – SD document: Delivery: Item data
Customer Tables:
KNA1 – General Data in Customer Master
KNB1 – Customer Master (Company Code)
KNB5 – Customer master (dunning data)
KNBK – Customer Master (Bank Details)
KNVV – Sales area data
Pricing Tables:
KONV – Conditions (Transaction Data)
KONH – Conditions (Header)
KONP – Conditions (Item)
Billing Tables:
VBRK – Billing Document: Header Data
VBRP – Billing Document: Item Data
Shipping Tables:
VEKP -Handling Unit – Header Table
VEPO – Packing: Handling Unit Item (Contents)
Vendor Tables:
LFA1-Vendor Master (General Section)
LFB1-Vendor Master (Company Code)
LFB5-Vendor master (dunning data)
LFBK -Vendor Master (Bank Details)
regards
rama

Similar Messages

Required SAP SD process Flow PPT's

hi Sd Guru's
i required SAP SD process Flow PPT's for KT session purpose so if anyone got this please send me to [email protected]
thanks &regards
tharakjram

hi Sd Guru's
i required SAP SD process Flow PPT's for KT session purpose so if anyone got this please send me to [email protected]
thanks &regards
tharakjram

Urgent : kanban process flow

Hai pp guru's
Any one please send the kanban process flow ppt .
I have to submit seminar for this month end .
very urgent.

Hai arun
Thank you yaaar....any other link for kanban, please forward .

Process flow for SD

Hi All,
Could you pls send me the process flow PPT for SD @ the following e-mail ID. [email protected]
Regards
Nishant

SD flow 1. Enquiry and quotation 2. Sales order (Which Customer, from which plant, delivery payment terms, quantity and rate) 3. Delivery (With out post goods issue no owner. In with out PGI no account document only material document ex: - Factory plant to port or with post goods issue- with owner. In this PGI accounting transaction done, ex: - Factory plant port customer. Entry is Invoice /decrease in stock Dr to in finished goods.
SD Integration steps: - 1. Define region 2. Define sales organization 3. Determine distribution channel 4. Define shipping point 5. Assign sales organization to company code 6. Assign distribution channel to sales organization 7. Assign division to sales organization 8. Setup sales area 9. Assign sales org- distribution channel plant 10. Define rules by sales area 11. Assign shipping point to plant 12. Define pricing procedure determination 13. Define tax determination rules. Testing: - 1. Creation of GL master sales local (Go29 revenue) 2. Assign GL accounts (NKOA) 3. Setup partner determination 4. Assign shipping points. User level 1. Creation of SD customer master (XD01)). And MM: - Movement types: -101 material receipt, 201 issue to cost center, 261 issue to order, 521 production receipts with out production order, 561 opening stocks, 601 delivery.

PPT on SD process flow

Hi guys am in need of help from u
am not so clear about the SD process flow
can anyone pls send me a PPT on SD process flow
to my email id:- (<REMOVED BY MODERATOR>).
thanking u in advance..
Regards
Jino.

Sales Organization   :
Responsible for:
     Distribution of goods and services
     Negotiating Sales Conditions
     Product Liability and rights of recourse
     A sales organization is uniquely assigned to a company code
     Master datas are separately maintained for a sales organization
     All items in the Sales and Distribution document belong to a sales organization
Distribution Channel:
Means through which products and services reach the customer
A distribution channel:
     Defines responsibilities
     Helps in achieve flexible pricing
     Differentiate Sales statistics
Division:
     A division is used to group products and services.
     A division represents a product line.
Sales Area:
A Sales area is a combination of
     Sales organization
     Distribution Channel
     Division
Each Sales and distribution document is assigned exactly to one sales area.
A sales area can belong to only one company code.
     Sales Organization
     Distribution Channel
     Division
                 Sales Area
Plant and Storage Location:
     A Plant is a location where stock is maintained
     Plant and storage location are used by all logistic area of R/3 System
     A Plant is uniquely assigned to a company code
Shipping point:
     Shipping point is the highest level of organizational unit in shipping
     Each outbound delivery is processed by one shipping point
     Shipping points are assigned to a plant
     More than one shipping point can be assigned to a plant
Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .
A Standard sales transaction has the following flow:
Inquiry
Quotation
Order
Delivery
Billing
The customer order management cycle begins with pre-sales activities.
A standard order in SAP contains:
     Customer and material info
     Pricing conditions
     Delivery dates and quantities
     Shipping info
     Billing Info
Inventory sourcing in SAP is taken care by
     Availability check
Shipping in SAP supports
     Outbound delivery creation
     Picking
     Packing
     Post Goods Issue
Billing in SAP supports
     Creating invoices for products and services
     Creating credit and debit memo
     Cancel previously posted billing documents
     Automatically transferring billing documents to accounting
When a billing document is created for a sales order we
     Credit the sales revenue account
     Debit the customer receivables account
Sales Document
A sales document is grouped into three structures
     Header
     Item
     Schedule Line
Outbound delivery
A delivery document is grouped into two structures
     Header
     Item
Several orders can be grouped into same outbound delivery if they have same
     Shipping point
     Delivery date
     Ship-to- address
Picking
     A transfer order is created for an outbound delivery
     A transfer order is created for a warehouse number
Post Goods Issue
When PGI is done the system
     Updates the quantity in inventory management and delivery requirements in materials planning
     Generates additional documents for accounting
     Adds the delivery to the billing due list
     Updates status in sales documents
Billing
We can group deliveries into single billing document if the deliveries have same
     Billing date
     Payer
     Destination Country
The effects of billing are
     Debit on the customer receivables account and credit on sales revenue account is created
     Sales information system
     Sales statistics is updated
Master data in SAP
SAP SD has got the following main masters:
     Customer master
     Material master
     Condition master
     Output master
     Customer material information master
Customer master
General Data                                         Sales Area Data          Company Code data
Tab pages                                              Tab pages                                      Tab pages
Address     Order             Accounting
Control data                                              Shipping               Payment
Payment terms                                          Billing               Correspondence
Marketing                                                   Partner functions                Insurance
Unloading points
Export data
Contact persons
The chart above shows detail on three main areas of customer master and the tab pages found under each area.
Material Master is maintained in different views and important views of sales and distribution are
     Basic data 1
     Sales Org 1
     Sales Org 2
     Sales : Gen/Plant
     Foreign Trade
     Sales text
Sales document in Sales and distribution mainly controls:
     Number range
     Item No increment
     Reference mandatory
     Item division
     Read info record
     Document pricing procedure
     Incomplete messages
     Alternative sales documents
     Delivery block
     Billing block
     Immediate delivery
     Delivery type
     Billing type
     Proposed delivery date
     Lead time for delivery
     Proposed pricing date
Plant determination in Sales and distribution:
To determine the plant in an order the system checks the master in the following order:
a)     Customer material info. record of the sold-to party
b)     Customer master record of the ship-to-party
c)     Material master record of the material
Shipping point determination
The following rule is used in determining shipping point in a sales order   :
Plant + Shipping condition (Sold-to-Party) + Loading group                  Shipping point
                                                      Maintained in Material master Gen: Plant data
Route determination
Route determined using the following rule in Sales and Distribution (SAP)
Departure Zone of Shipping Point
+
Shipping condition (Sold-to-Party)
+
Transportation Group (Material master)
+
Transportation Zone (Ship-to-Party)
Route
Delivery scheduling:
As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:
     Material availability date
     Transportation planning date
     Loading date
     Goods Issue date
     Delivery date
Availability Check in SAP:
     Availability check is carried out at item level for a plant
     Availability check is done on the material availability date
     If material availability date is in the past the forward scheduling is done, if not backward scheduling is done.
Item category determination in the order:
Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.
Sales document type
+
Item category group (Material master)
+
Item usage
+
Item category of higher level item
Item category of the item
Item category in a sales document mainly controls the following
     Relevance for billing of an item
     Billing block
     Pricing relevance
     Business data relevance item
     Schedule line allowed
     Item relevant for delivery
     Returns
     Determine cost
     Credit active
     Incompletion procedure
     Partner determination procedure
     Structure scope (relevant for bill of material explosion)
     Value contract material
     Contract release control
Schedule line category:
Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:
Item category + MRP type(Material Master)         Schedule line category
Schedule line category mainly controls:
     Delivery Block
     Movement type
     Item relevant for delivery
     Req/Assembly
     Availability
     Product Allocation
Copy Control:
Copy control is normally set for
     Header
     Item
     Schedule line levels
To control copying procedure we have
     Data transfer routines
     Copying requirements
     Switches
Pricing Procedure determination:
Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.
The major factors taken into consideration for pricing procedure determination is:
Sales area
+
Customer Pricing procedure(Customer Master Sales area data)
+
Document Pricing Procedure(Sales Document Type)
Pricing Procedure
What are the components of pricing procedure?
How is that a person should work on Pricing Procedure?
To start with first
Define a Condition table:
What is a condition table?
A table where the key fields are data combinations for which messages are triggered (and offered for processing).
For each data combination, there is a condition record in the table. The data part contains the actual message.
As mentioned above a condition table is a table which carries key fields for picking up the prices.
Define Access Sequences
The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.
Recommendation
     If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
     Do not change access sequences contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
Example
In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.
Define Condition Type
A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
Note
     The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
     You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
Recommendation
     If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
     Do not change the condition types which are contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.
Specify an alphanumeric key which can have up to 4 digits, and a textual description.
Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
3. Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
Define Pricing Procedures
The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.
SAP Recommendation
     Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.
     Do not change the pricing procedures contained in the standard SAP R/3 System.
Actions
1. Create new pricing procedures by copying a similar pricing procedure.
o     Specify a key with up to 6 characters and a description.
o     For a procedure, specify the condition types in the sequence of their usage.
Maintain the lines of the pricing procedure
2. Afterwards define the customer determination procedures for determining the procedure.
3. Define the document pricing procedures for determining the procedure.
4. Assign the procedure to the sales document types and billing types.
5. To determine the procedure, define the allowed combinations of:
o     Sales area
o     Customer pricing procedure
o     Document pricing procedure
o     Pricing procedure
Shipping:
The basis for shipping is delivery.
Delivery document controls the following in deliveries
     Number range
     Item no increment
     Storage location rule
     Route determination
     Text determination
     Delivery split
     Gen. packing material / item
     Order required
Delivery item category controls:
     Check min delivery
     Availability check
     Relevant for picking
     Storage location required
     Determine storage location
     Automatic batch determination
     Text determination procedure
Billing:
Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.
Billing document has got the following structure:
     Header
     Item
Billing documents mainly control:
     No. range
     Posting block (Controls posting to accounting)
     Relevant for rebate
     Account determination procedure
     Account determination recon account
     Account determination pay.cards
     Output determination procedure
Account Determination in SAP
Account determination in SAP-SD happens with the following rule
Sales Organization
Chart of Accounts
Account assignment group Customer
Account assignment group-Material
Account Key
G/L account on which the postings has to happen.
CHeers!!!

Process Flow Diagram

Can someone provide me with a process flow diagram and the step for creation of returnable packaging ?
Thanks
Logi

Hi,
For returnable pacaging,you have to create a material with "LEIH" material type.
Pls go through the following link for process flow daigram:
[Process flow for LEIH material type|http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_Overview_73_EN_PE.ppt]
Pls go through the following link for process flow of shipping:
[Process flow of shipping|http://help.sap.com/bp_bl603/BBLibrary/Documentation/107_Scen_Overview_EN_US.ppt#488,1,Sales Processing Using Third Party (with Shipping Notification) SAP Best Practices Baseline Package (U.S.)]
Hope this is what you are looking for.And this will help you also.
Regards,
Krishna.

Business Process Maps/ Process Flows for Retail Operations

Dear All,
I am looking for Business Process Maps/ Process Flows for Retail Operations like forecasting, inter store transfers, ASN, Procurement, Allocation etc.
Kindly provide me with a link, docs, PPts etc.
Appreciation would be in the form of points.
Regards,
Jack Silverz

Hi Jack
Seeing as you only got one reply - I'm jumping in with my 2-peneth.
Seldom have I found process content which sufficiently explains both manual and automated processes in a format which is sufficiently simple to engage discussion (between project teams and business representatives). Is there a way to strike the required balance - simplicity for the sake of engagement; yet rich enough to record SAP dependencies, system requirements and so forth.
An answer in my opinion is [here|https://ecohub.sdn.sap.com/irj/ecohub/solutions/control2007]. (Honest account - I work for Nimbus. But you don't have to take my word for it. Check out our case studies if you like. This approach is being adopted by several strategic SAP accounts several of which are listed [here|https://ecohub.sdn.sap.com/irj/ecohub/solutions/control2007]).
What might partly address your requirement is the [APQC Process Classification Framework|http://www.apqc.org/portal/apqc/site/?path=/research/pcf/index.html] . We took this framework as a starting point for building a model company process map. I cannot claim that it is Retail specific, but we have quite a few retail customers who have adopted Control 2007 and also several supply chain optimization projects which we have delivered.
If this is of interest - we provide a web hosted demonstration environment where you can explore the APQC process content I mentioned above. You can contact me through [SAP EcoHub|https://ecohub.sdn.sap.com/irj/ecohub/solutions/control2007] for more details
Kind regards, Nigel

FICO standard process flow diagrams

Hello,
Can anyone provide me any documentation or link for standard SAP FICO process flow diagrams?
I even looked at SAP Best practices but could not find any FICO specific process flow diagrams there.
Thanks and regards
Kedar

Hi,
These is related costing
http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_overview_03_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_overview_04_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_overview_05_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_overview_06_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_overview_07_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_overview_08_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/184_Scen_overview_EN_MY.ppt
http://help.sap.com/bp_bl603/BBLibrary/Documentation/185_Scen_overview_EN_MY.ppt
http://help.sap.com/bp_bl603/BL_MY/Html/scope/Scoping_offline_SC.htm?display=STE- L_MY_V1603+ENTRY_LEVEL_FINANCIALS.xml
regards,
Santosh kumar

URGENT:error while deploying a process flow

EMP_COUNT is a mapping which i have deployed .
when i try to deploy a process flow i get the following error:
OMB05602: An unknown Deployment error has occured for Object Type API8028: No signature is available for mapping EMP_COUNT because the generation language is undefined. Please set the generation language property of this mapping, or generate this mapping to set the generation language property to a default value..
thnx in advance

OMB+> OMBALTER MAPPING 'EMP_COUNT' SET PROPERTIES (GENERATION_LANGUAGE) VALUES ('PLSQL')
Fast enough? ;-)
Regards,
Detlef

Cannot deploy process flow package specification from file

Hi,
we are using owb 11gr2 on linux. We successfully managed to deploy mappings and tables into a specification file, and then deploy from that file into the target database (RAC). But when we try to deploy a process flow package we run into an error:
A process flow package can be deployed to a specification file. But a deployment from that specification file fails with the error: " OMB05623: Cannot deploy specification from file. Exception follows. nulll"
### SETUP
set CONN_DESIGN "xxx"
set CONN_TARGET_DESIGN "yyy"
set CONN_TARGET_RT "xxx'"
set DIR "D:\\tmp"
set RELEASE "V0_2"
set file "$DIR\\$RELEASE"
set plan "FILE_DEPLOY_$RELEASE"
### Deployment via control center: works!
OMBCONNECT $CONN_DESIGN
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
OMBCC '/KLINGEL_DWH'
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan'
OMBDISCONNECT CONTROL_CENTER
OMBCOMMIT
OMBDISCONNECT
### Deployment via specificatin file: fails!
OMBCONNECT $CONN_DESIGN
OMBCONNECT CONTROL_CENTER $CONN_DESIGN
OMBCC '/KLINGEL_DWH'
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan' AS SPECIFICATION TO '$file.xml'
OMBDROP DEPLOYMENT_ACTION_PLAN '$plan'
OMBDISCONNECT CONTROL_CENTER
OMBCOMMIT
OMBDISCONNECT
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
OMBDEPLOY SPECIFICATION FROM '$file.xml'
### OMB05623: Deployment von Spezifikation aus Datei nicht möglich. Exception folgt. null
###OMB05623: Cannot deploy specification from file. Exception follows. nullIf we use the operation DROP it works. But REPLACE and CREATE do not work.
We get the error regardless whether the code is executed as an expert or on the command line at a windows client.
Does anyone knows a workaround?
Deployment via a specification file is a must due to license and architecture requirements.
Thanks,
Carsten.

Its woked fine for me for OWB 10.2.0.4 .... some steps are missing from code like
when you are connecting again it should be
OMBDISCONNECT
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
OMBDISCONNECT
OMBCC '/KLINGEL_DWH'
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RTI think you can try the same on different system .
Cheers
Nawneet

A/R process flow with notice of readiness for shipment

Hi,
I'm trying to implement the following A/R process flow:
- sales order
- xx% A/R down payment invoice
- notice of readiness for shipment
- incoming payment
- delivery
- A/R invoice (xx% down payment to be deducted here)
What's the best way to implement it?
Thanks
Fabio

Hi,
no, it's something different. It is because we want to be paid before shipping anything.
In more detail:
- we request a certain amount of down payment after the order and before starting production
- we request final payment before we deliver goods
Thanks
Fabio

MM - PO process flow chart

MM Gurus , Can any one help me to provide me with the MM PO and Change PO process flow diagram .Pl send me the diagram or links to my email ID
Thanks in advance .Will give you points
James
[email protected]

Dear James,
Process Flow:
1)Determination of Requirements: Through MRP, purchase requisitions
2)Source Determination: helps you identify potential sources of supply, creating requests for quotation (RFQs
3) Vendor Selection and Comparison of Quotations: The system is capable of simulating pricing scenarios
4) Purchase Order Processing: information from the requisition and the quotation to help you create a purchase order. scheduling agreements and contracts are also supported.
5) Purchase Order Follow-Up: The system checks the reminder periods you have specified. up-to-date status of all purchase requisitions, quotations, and purchase orders.
6) Goods Receiving and Inventory Management: Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number
7) Invoice Verification: The system supports the checking and matching of invoices, and clearing invoices for payment.
Flow Chart for PO & MM process :
RFQ (ME 41) --> Maintain Quotation ( ME 47) -> Price comparision ( ME 49)>
-->Create PR ( ME 51 N) --> Create PO ( ME 21N) --->
> Good Receipt wrt PO( MIGO)> Invoice Verification wrt PO ( MIRO)
I hope this will suffice your need & if satisfied please reward points,
Vivek

Demo on SAP Transportation Management Overview + End to End Process Flow by Navin Nadpurohit-SAP TM Consultant - Krypt Inc-a Leading SAP Supply Chain Company

Hello All,
Attached is the link explaining SAP Transportation Management Overview and a system demonstration of End to End Process Flow.
Link:
TM Overview + End to End Process Flow - YouTube
Thanks and best regards,
Navin

Very Good Demo Navin

RPE-01008: Recovery of this request is in progress in process flows.

Hi,
I am calling shell script as an userdefined activity in a process flows.
All the process flows were working fine.
Today, all the process flows wherever the shell script is called ended up with an error showing " RPE-01008: Recovery of this request is in progress".
Could any one please explain, what might be reason?
Thanks in advance.
Thank you,
Regards,
Gowtham Sen.

Hi,
we have exactly the same problem here.
Does anybody have a solution?
regards
Lutz

To check whether a process flow is valid or not

Hi,
I want to check whether a OWB process flow is valid or not inside a PL/SQL block. Can anyone let me know about any repository table or view where I can check the process flow status.
Regards,
Poulose

Use display schedule job option from the context menu of the start variant of the process chain.
When u chick this.. u will get the available job on this start process.. There u can see whether the process chain in schedule mode or not?
If u can see multiple schedule then u can delete the older ones which are not needed and then u can maintain only one schedule job.
If u click twice.. then there are chances that u might end up with the 2 schedule job with the same time frame.. .. so check the same with the steps mentioned..... if u find two jobs then u need to delete one.. if not there might be chance that ur PC might get trigger twice.. and one trigger will gets failed. and the other one will gets executed..
Thanks
I hope this is clear to u..
Assign points if this helps

SD PROCESS FLOW PPT

Similar Messages

Maybe you are looking for