What is the flow of FI ?

hi,
I am an abap consultant interested to know FI i want to know what is the flow involved in FI like how is data is distributed among from where it starts and and ends and wht ar major tables involved ? Thank you in advance

Hi,
Check for Tables and flow to other modules from this link
http://www.erpgenie.com/sap/abap/tables_fi.htm
Rgds.

Similar Messages

Can any one share what is the flow of mm

HI
GURUS WHAT IS THE FLOW OF MM
THANKS IN ADVANCE

Hi,
MM Process Flow
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an 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. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment
Reward if useful
Chandru

What is the flow of Oracle Manufacturing

Hi,
what is the flow of oracle manufacturing . If any one know pls help me.

Hi,
PO Flow
http://sap-img.com/materials/what-is-the-dataflow-of-mm.htm
SD Flow:
http://www.sap-basis-abap.com/sd/sap-sd-processing-flow.htm
http://www.sap-basis-abap.com/sapsd.htm
MM Flow:
http://www.erpgenie.com/sap/sapfunc/mm.htm
FI :
http://www.thespot4sap.com/IntroTo/SAP_FI_Module_Introduction.asp
http://www.thespot4sap.com/IntroTo/SAP_CO_Module_Introduction.asp
See the below thread for more info
Re: reg : document flow for SD and MM ?
mark all the helpful answers
Regards
Sudheer

What is the flow of BPC?

Hi,
I am new in BPC can anyone please help that what is the flow in BPS and what are the common and useful tcodes in BPC.
Also i am in BPC Security part so need information regarding the materials on BPC Security.

Hi,
PO Flow
http://sap-img.com/materials/what-is-the-dataflow-of-mm.htm
SD Flow:
http://www.sap-basis-abap.com/sd/sap-sd-processing-flow.htm
http://www.sap-basis-abap.com/sapsd.htm
MM Flow:
http://www.erpgenie.com/sap/sapfunc/mm.htm
FI :
http://www.thespot4sap.com/IntroTo/SAP_FI_Module_Introduction.asp
http://www.thespot4sap.com/IntroTo/SAP_CO_Module_Introduction.asp
See the below thread for more info
Re: reg : document flow for SD and MM ?
mark all the helpful answers
Regards
Sudheer

What is the flow of contollers load/execution in a Web Dynpro applicatio

Hi Frndz..
As we now that we have the controllers in WDP like
1)Component contriller 2)CustomControoler 3) View Controller 4)Interface Controller 5) Interface view Controller.
Now i want to know what is the flow of thse controllers will load and execute when we run an Web Dynpro app.

Hi Rajesh
In general, dependent nodes are represented by a single node instance, whose content - that is, its node collection - changes each time the lead selection of the parent node changes. Such context nodes are known as single nodes.
This means that the user can only access data of the child nodes that belong to the code element (lead selection) currently selected in the parent node. Therefore, Web Dynpro allows you to define additional non-singleton nodes. Each non-singleton node has one node instance for each node element of the parent collection at runtime.
The advantage is that each instance can be accessed directly. When using non-singleton nodes, the nodes are only created when the node values are retrieved. This can save resources that otherwise would slow down the performance of the application.
Note that singleton nodes should only be considered singleton in relation to their parent nodes but not in relation to the context. Each instance of a non-singleton parent node has exactly one instance of the singleton node.
The singleton property can be defined for all dependent context nodes. It is either true or false:
- singleton = true: Newly defined context nodes are of type singleton by default. This means that a child node instances exists for each parent node, not for each node element in the parent node. The content of the child node, that is, the list of the node elements it contains, changes each time the lead selection of the parent node changes.
- singleton = false: A child node instance exists for each node element in the parent node. The content of this node instance does not change. The node instances of the child node can be accessed using generated context interfaces.
The varying relation between child and parent nodes is important for singleton and non-singleton nodes. Whereas singleton nodes are related to the parent node, non-singleton nodes always refer to a node element of the parent node at runtime.
Child nodes of type Singleton always refer logically to an element of the parent node, that is, the one in the lead selection. If the parent node does not have a lead selection, then the singleton child node is invalid, even though it exists.
Supply function
A supply is needed primarily to populate a singleton node's element collection.
Any context node can have a supply function defined for it.
Check this link for supply function
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60086bd5-9301-2b10-6f97-a14366a5602b
Thanks,
Tulasi
Edited by: Tulasi Palnati on Jan 28, 2009 12:43 PM

What's the flow of learning J2EE at present?

I know that many techniques are emerging nowadays. I studied J2SE already. Now I want to learn J2EE development. Who can tell me what's the structure and the flow to study J2EE?

start with servlets, JSPs, JSTL, and JDBC. You can go a long way with those.
when that feels comfortable, learn Spring.
No need for EJBs.
%

What is the flow of sd

hI
inq,qt,or,del,invoice
or
inq,qt,or,.del,shipment,invoice

hi
SD process starts with
1. creation of Inquiry - VA11
2. Create Quotation - VA21
3. Create Order- VA01
4. Create Delivery - VL01N
5. Picking (create Transfer Order) - Lt03
6. Confirm TO - Lt12
7. DO PGI - VL02N
8. Create INvoice - VF01
9. POst INcoming Payment - F-28
Third-Party Order Processing with Shipping Notification:
This SAP best practice supports passing a customer order to a third-party vendor, who then ships the goods directly to the customer, bills you, and sends you a shipping notification. The shipping notification received is entered as a dummy goods receipt in consumption. This approach allows you to create the customer invoice before you receive the incoming invoice from the vendor.
The following functions are provided to support the Third Party With Shipping Notification:
Order
When the order is created, the specification of material numbers, quantity and conditions takes place at item level. As the material is not available on stock, a purchase requisition is created directly within the sales order.
Purchase Order Processing
The purchase requisition can already be automatically assigned during creation. If not, it is possible to assign the purchase requisition manually. The purchase order is created with reference to the purchase requisition. Quantity and material are transferred from the sales order. The purchase order price can also now be determined via the condition records.
Shipping Notification
When the vendor has sent the material to the customer, they will normally send you a shipping notification, which, amongst other things, contains the exact quantity of material sent. You have the possibility to enter this shipping notification into the system in the form of a dummy goods receipt. It will be posted directly in consumption so that no stocks are created. The quantity of goods received then updates the quantity to be invoiced in the sales order. Therefore, it is possible to create the customer invoice before you receive the incoming invoice from the vendor.
Billing Documents
The billing documents are created on the basis of the order. Since the vendor might not deliver the exact quantity ordered, quantity adjustment takes place via the shipping notification.
Vendor Invoice Verification
The vendor invoice verification can take place after billing. The variance in purchasing can be updated in Controlling using retroactive billing.
Controlling
The revenue and costs will be posted to CO-PA using the billing document.
Third-Party Order Processing Without Shipping Notification:
This SAP best practice supports passing a customer order to a third-party vendor, who then ships the goods directly to the customer and bills you. The vendor does not send a shipping notification. The incoming invoice from the vendor updates the billing quantity, so that you can create the customer-billing document only after entering the invoice from the vendor.
The following functions are provided to support Third Party Without Shipping Notification building block:
Order:
When the order is created, the specification of material numbers, quantity and conditions takes place at the item level. As the material is not available on stock, a purchase requisition is created directly within the sales order.
Purchase Order Processing:
The purchase requisition can be automatically assigned during creation. If this is not the case, it is possible to assign the purchase requisition manually. The purchase order is created with reference to the purchase requisition. The amount and the type of material are transferred from the sales order. The purchase order price can be determined via the condition records.
Vendor Invoice Verification:
The vendor invoice verification is to be performed before customer billing. The quantity of the invoice updates the quantity to be invoiced in the sales order.
Billing Documents:
The billing documents created are based on the sales order. Since the vendor might not deliver the exact quantity ordered, quantity adjustment takes place via the vendor's invoice.
Controlling:
The revenue and costs will be posted to CO-PA via the billing document
Stock Transfer Order:
Whenever you need to transfer the materials from one plant to another plant belonging to one company or belonging to two company code stock transfer order is raised by the delivering company.
Transfer of goods from one location to another location,it may be between plants within the same company code or in different company code's plants.
within the company code, bet plants, receiving plant will raise the STO in Supplying/issuing plant-ME21n,
Supplying plant will deliver the goods to receiving plants , then we need to pick n post the Goods Issue-VL02n, nw when we can observe that the STO qty will be added into receiving plant and reduced in Delievering plant.
To do this, we need do prior customizatin in SPRO-IMG,-material should be created in both plants( receiving & Supplying)
-maintaing the stock only in supplying plant
-create a dummy customer in supplying plant's sales area(if u have one sales area, create in tat comp code n sales area)
-Assign this customer number to receiving plant's details along with the sales area,
-Assign the STO doc type(UB) to Supplying plant, along with checking rule
-Assign the Del type (NL/NLCC) to Supplying n receiving plant.
You create a STO from MM route i.e., ME21N and then enter the details of the supplying,receiving plant and the materials.Once you complete the STO,then it goes for a delivery followed by an intercompany invoice.
Remember that the Material should be there in BOTH supplying and receving plant.
Internal Procurement (Stock Transfer With Delivery):
In a company, goods movements do not only occur in the form of goods receipts and goods issues. Depending on the organization of the company (for example, decentralized storage) and its sales policy, internal stock transfers might also be necessary.
The stock transfer with delivery is a plant to plant scenario. You are posting a goods issue in plant BP02 and a goods receipt in plant BP01.
This type of stock transfer can only be carried out from unrestricted-use stock of the issuing plant to unrestricted-use stock of the receiving plant.
You post the placement into storage at the receiving plant in a second step. Only then is the event completed and the transferred quantity part of unrestricted-use stock.
Functions:
Creating a Planned Independent Requirement
Creating a stock transport order in plant BP01
Generating a delivery in plant BP02
Picking of the material and posting the goods issue in the delivering plant
Posting the goods receipt in the receiving plant
Note: The quantity posted from stock is first of all managed as stock in transit of the receiving plant. Only once the goods receipt has been posted is the quantity posted to the unrestricted-use stock of the receiving plant. This enables the quantity "on the road" to be monitored.
The transfer posting is valuated at the valuation price of the material in the issuing plant.
Delivery costs can be entered in the stock transport order.
Internal Procurement (Stock Transfer without Delivery):
The cross-plant, internal procurement of materials can be carried out within one company code (intercompany) or by using several company codes (cross company). This process can be dealt with using standard functions such as material requirements planning, purchase requisition, stock transport order, transportation planning and the handling of internal deliveries.
The following functions are provided to support the Internal Stock Transfer without Delivery:
Create Stock Transport Order
Post goods issue for stock transport order
Post goods receipt for stock transport order
Note: Quantity "on the road" can be monitored
Delivery costs can be entered in the stock transport order
Internal Procurement (Cross-Company Stock Transfer):
You post a stock transfer from company code to company code the same way as you post a stock transfer from plant to plant, except that both plants belong to different company codes.
During the stock transfer, two accounting documents are created in addition to the material document:
-An accounting document for the removal from storage at the issuing company code
-An accounting document for the placement into storage at the receiving company code
The stock posting is offset against a company code clearing account.
To display the value of the cross-company-code stock in transit with a report, choose Environment à Stock à Stock in transit Cc.
The following functions are provided to support the cross company stock transfer:
Create sales order to customer
Run single-level MRP
Creating a purchase order
Creating delivery
Picking and post goods issue
Posting goods receipt
Create inter-company billing document
Invoice receipt
Create delivery, picking and post goods issue to customer
Billing
Notes: The issuing plant enters a delivery for the stock transport order and a billing document. This is an inter-company billing document (billing type YBIV). Pricing takes place as normal.
When the goods arrive, the receiving plant posts a goods receipt for the purchase order. The unrestricted-use stock increases and an accounting document is created.
The invoice is checked with reference to the purchase order.
Stock transport order processing in receiving plant
Delivery processing in supplying plant Picking batch determination in delivery Goods issue processing in the supplying plant Billing processing in supplying plant
Goods receipt processing in receiving plant Invoice verification processing in receiving plant Purchase order monitor processing in receiving plant
Process involved ::
     Inquiry Processing
     Quotation Processing
     Contract Processing
     Sales Order Processing
     Scheduling Agreement Processing
     Returns Processing
     Rebate Processing
     Sales Deal and Promotion Processing
     Display Customer and Material Information
     Billing Processing (online)
     Billing Processing (In The Background)
     Invoice List Processing
     Maintain Customer and Material Information
     Display Pricing
     Maintain Pricing
     Release Blocked Documents for Billing
     Release Sales Orders for Delivery
     Display Sales Information
     Display Billing Documents
     Sales Analysis
     Credit Management in Sales and Distribution Documents
     Backorder Processing
     Sales Support
     Output Processing
Inquiry Processing
     Create/change/display inquiries
     Generate lists for inquiries and incomplete inquiries
     Select sales documents according to object status
Quotation Processing
     Create/change/display quotations
     Generate lists for quotations and incomplete quotations
     Select sales documents according to object status
Contract Processing
     Create/change/display contracts
     Generate and process list of contracts
     Generate and process list of incomplete contracts
     Select sales documents according to object status
Sales Order Processing
     Create/change/display sales orders
     Generate and process list of sales orders
     Generate and process list of incomplete sales orders
     Select and process sales documents according to object status
     Select and process sales documents in a period of time
     Select and process duplicate sales documents in a period of time
Scheduling Agreement Processing
     Scheduling agreement processing
     Select and process incomplete scheduling agreements
     Select sales documents according to object status
Returns Processing
     Create/change/display sales orders
     Create/change outbound delivery
Rebate Processing
Rebate processing:
     Maintain rebate agreements
     Extend rebate agreement
     Settlement of rebate agreements
     Generate list of rebate agreements
Billing document:
     Display billing document
     Compare the rebate basis from billing documents and statistics
     Update billing documents referring to rebate conditions
Sales Deal and Promotion Processing
     Create/change/display sales deals
     Generate list of sales deals
     Create/change/display promotions
     Generate list of promotions
Display Customer and Material Information
     Display customer (Sales)
     Display material
     Display material listing/exclusion
     Select customer material info record according to customer
     Select customer material info record according to material
     Display customer hierarchy
     Display sales deals
     Display promotions
     Display rebate agreements
     Display cross selling materials
     Display assortment module for value contracts
Billing Processing (online)
     Create/change/display billing document
     Cancel billing document
     Retroactive billing
     Process billing due list
     Set billing date
     Display billing documents from the archive
     List of billing documents
     Rebook accounting indicator
     Release sales orders for billing
     Display sales and distribution documents blocked for billing
Billing Processing (In the Background)
     Display billing document
     Generate batch jobs for billing
     Generate log for billing document run
Invoice List Processing
There are two types of invoice lists in the Standard:
1.     one for invoices and debit memos
2.     one for credit memos
     Create/change/display invoice lists
     Process work list for invoice lists
     Generate invoice list
     Generate cancellation invoice list
     Display invoice list from the archive
Maintain Customer and Material Information
     Maintain material listing/exclusion
     Reference material listing/exclusion
     Maintain material substitution
     Reference material substitution
     Maintain material information
     Select customer material information according to material or customer
     Maintain material
     Maintain customer (Sales)
     Maintain customer hierarchy
     Maintain materials for cross selling
     Maintain value contracts
     Maintain Incoterms
Display Pricing
     Display condition records
     Display condition lists
     Display conditions using index
     Display free goods determination
Maintain Pricing
     Create/change/display condition
     Condition processing using index
     Create/change/display free good
     Create/change/display condition lists
     Process net price list
     Release expected customer price
Release Blocked Documents for Billing
     Release sales orders for billing
     Change billing document
     List of blocked billing documents
Release Sales Orders for Delivery
     Change sales order
     Block and unblock customer from sales view
     Generate lists for incomplete sales documents and for sales documents blocked for delivery
Display Sales Information
     Generate list for quotations, contracts, sales orders or scheduling agreements
     Generate list for incomplete quotations, contracts, sales orders or scheduling agreements
     Generate list of sales orders blocked for delivery
     Display sales activities, item proposals, material listing and material exclusion
     Sales support monitor
Display Billing Documents
     Display billing document
     Display list of billing documents
     Display blocked billing documents
Sales Analysis
     Contracts: Lists for overdue and completed contracts
     Quotations: Lists for overdue and completed quotations
     Backorder processing: Backlog list, selection list
     Generate list for: Inquiries, rebate agreements, scheduling agreements
     Information on the customer: Sales summary, list of top customer
     Material information: List of top materials
     Sales support monitor
     Flexible planning: Display/create/change
Credit Management in Sales and Distribution Documents
     Process credit authorization for sales and distribution documents
     List of released sales and distribution documents
     List of blocked sales and distribution documents
     Process credit authorization according to sales and distribution document
     Process credit authorization according to delivery
     List of incomplete sales and distribution documents
     Sales and distribution documents blocked for delivery
     Delivery monitor
     List of billing documents
Backorder Processing
     Display backlogged sales orders
     Process backorder processing using selection list according to sales documents
     Backorder processing: access using the material
     Execute rescheduling of sales documents
     Evaluate rescheduling of sales documents
Sales Support
     Create/change/display sales activities
     Executing mailing promotions
     Display and create interested parties and contact persons
     Display sales summary
     Sales support monitor
     Display competitive products
Output Processing
     Display/change/create output-condition records in Sales
Reward if USeful
Thanx & regards..
Naren..

What are the benefits of using a namespace, such as 'flow'?

In the past week I started to delved thru several blogs, livedocs and api articles on TLF, and noticed in some XML data to be used in TLF uses a namespace, such as 'flow'. What benefits are there currently and/or in the near future of using them? And is it advisably to have exisiting data to use a namespace?
By the way, this framework gives me goosebumps. Can't wait to start producing some work from it.

The main reason to use a namespace is if you want to use some of your elements, and don't want to have to worry about name collisions. But you can make the tlf namespace (or any other) the default namespace, and then you don't have to use the flow: prefix everywhere.
Glad you're looking forward to writing code on TLF! Let us know how it goes for you.
Thanks,
- robin

What is the best expression to name the planning flow on SAP?

I am working on my graduating project in this topic: configuring the planning flow on SAP for the different types of industries.
By planning flow, I am talking about S&OP -> Demand Management -> MRP. But what's the best way to refer to this flow?
I already thought about:
"industrial planning" but it's too general and not precise.
"production planning" but it already refers to the PP module, which deals with other functions than what i am meaning.
"logistic planning" but it refers mainly to the operational level (ressources, workshop management, scheduling) while my work stops at MRP (tactical level)
Can you help me to find the best designation?

OK, I got it now... You are going to love this!
"Advanced Planner and Optimizer", or in short "APO".
The abbreviation even has a website shortcut already www.sap.com/apo and there is a whole instant community already there waiting for you.
What a bargain! :-)
Cheers,
Julius

What is the process flow in MRP - MD61+MD01,MD02+MD04+COR7

Hi experts,
I need one clarification for Material requirment planning ( MRP - Process industries )
My company is newly implemented in SAP so i want some clarification in MRP side. My company flow is 3 rd level converted of FG.
1 st level - Raw paint - Samifinished
2 nd level - Tin condition - Samifinished
3 rd level - Case condition - FG
I have raised PIR in MD61 at FG code, after MRP Run planded order created at three level ( 1 st, 2nd, 3rd - level)
But what is the t.code used is correct recording MRP Run - MD01( Plant level ) OR MD02 ( Single item)
what is the t.code used for over all requirment Bill of material list ( ROH & VERP)at plant based recording purchase the material.
Kindly pls explain the flow for PIR > MRP RUN>STOCK RECUIRMENT LIST> PLANNED ORDER TO PROCESS ORDER>
Thanks,
Umapathy

Hi,
To proceed further you should firm confirm that below master data properly maintained in your system,
- Create BOM - CS01
- Create Resource - CRC1
- Create Master Recipe - C201
Now your business process starts with the requirements created in the system e.g. by MD61 in your case
Now you can run the MRP by MDBT/MD01/MD02 for your case. It is suggested to go with MD02 for better understanding on MRP behavior for single FG material.
Now You can analyze the MRP result for single FG material in MD04 transaction wherein you will get the planned order created through MRP run and also the order report for planning of below level components of BOM
Then you can further proceed for Production Execution with the help of below transactional steps:-
- COR1 - Create Process Order Manual
- COR7 - Convert Plan Order to Process Order
- COR6N/CORZ/CORR - Order Confirmation
- CORS - Cancel Confirmation
- CORT - Display Confirmation
- CO53 - Control Recipe Monitor (Optional)
- CO55/CO60 - Maintain PI Sheet (Optional)
- CO54 - Process Massage Monitor (Optional)
- MB31 - Goods Receipt For Order
- COIK / MB1A / MIGO :- Goods Issue
- KKS1/KKS2 - Calculate Varience
- CO88 - Actual settlement
- COOISPI - Order Information System
You can see the all PR created through MRP in ME5A transaction by selecting the Creation Indicator as B for MRP as shown in below screen,
And for rest of analysis you can use COOISPI report.
Regards,
Narresh

What is the best practice to display info of completed task in process flow

Hi all,
I'm starting to study BPM modeling with CE7.1 EHP1. Thanks to the tutorial and example on SDN site and I can easily build my own process in NWDS and deploy to server, start it, finish it.
I like the new runtime which can show a BPMN diagram to the processors. However, I can't find a way to let the follow up processor to review the task result completed in previous step. I'm more familiar with Guided Procedure, and know there is "Display Callable Object" which can used to show some info of a completed task when the processor/owner/admin/overseer click on a completed task. Where is the feature in BPM ? What is the best practice to show such task information in BPM environment.
For example, A multiple level approval process, the higher level approver need to know the comment written by the previous approver. Can he read this information from process flow ?
I think it is very important feature for a BPM platform. In Guided Procedure, such requirement can be done with Display Callable Object + View Permission, and you just need some coding for the UI. If BPM is superior to GP, I think there must be a way to achieve this, I just do not know how ?
Can anyone shed me some light on it ?

Oliver,
Thanks for your quick reply.
Yes, Notes and Attachment CAN BE USED for the purpose. But I'm still looking for a more elegant solution.
With the solution of using Notes/Attachment, the processor need to give input at two places : the task UI and Note/Attach , with similar or same data. It is really annoying.
Is there any SAP BPM real-world deployment ? None of customer has the requirement ?

WHATS THE FLOW OF A PURCHASE ORDER WITH REGARS TO MATERIAL MANAGEMENT ?

WHATS THE FLOW OF A PURCHASE ORDER WITH REGARDS TO MATERIAL MANAGEMENT ?

Hi
see the MM flow with related Transaction codes
MM Cycle:
Purchase Requisition-> Staff in an orgn places Pur requisition for want of some goods/products - ME51
Request for Quotation(RFQ)-> The Purchase dept in the orgn calls/requests for the quotation for the products against which PR was raised. - ME41
Vendor Evaluation->After receving the RFQ's, after comparison a Vendor is finalised based on the terms and conditions.
Purchase Order(PO)-> Pur order was issued to that vendor asking him to supply the goods/products -ME21N
Goods Receipt Note(GRN)->Vendor supplies the material/Products to the orgn-
MB01
Goods Issue (GI) -> People receives their respective itesm for which they have placed the Requisitions
Invoice Verification-> ALong with the Material Vendor submits a Invoice for which the Company Pays the amount - .MIRO
Data to FI -> data will be posted to FI as per the vendor invoices
you better go through all these links u will get all the info what ever u need
for mm
http://www.sapgenie.com/abap/tables_mm.htm
http://www.sap-img.com/sap-download/sap-tables.zip
http://www.allsaplinks.com/material_management.html
http://www.training-classes.com/course_hierarchy/courses/2614_SAP_R_3_MM_Invoice_Verification_-_Rel_4_x.php
http://www.sapfriends.com/sapstuff.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOMDMM/LOMDMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMIVMVAL/MMIVMVAL.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMWMLVS/MMWMLVS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMISVE/MMISVE.pdf
Reward points if useful
regards
Anji

What is the best practice in order to create flow in a single maintenance plan?

Hi All,
What is the best practice in order to create flow in a single maintenance plan.
1st Check Database Integrity (Check DB)
2nd Rebuild Index
or
1st Rebuild Index
2nd Check Database Integrity (Check DB)
Grateful to your time and support. Regards, Shiva

Use the Maintenance Plan Wizard to create a maintenance plan:
"This topic describes how to create a single server or multiserver maintenance plan using the Maintenance Plan Wizard in SQL Server 2012. The Maintenance Plan Wizard creates a maintenance plan that Microsoft SQL Server Agent can run on a regular
basis. This allows you to perform various database administration tasks, including backups, database integrity checks, or database statistics updates, at specified intervals."
LINK: http://technet.microsoft.com/en-us/library/ms191002.aspx
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

*what is the difference between web flow engine and sap business workflow?*

Hi,
Can any please guide me by telling what is the difference between web flow engine and sap business workflow?

>
Arghadip Kar wrote:
> Check this link
>
> http://www.workflowing.com/id35.htm#1__what_is_the_difference_between
... which is exactly where the FAQ item came from!

What is the Data flow in SAP-BPC NW

Hi All,
Could any body explain me how the data is flowing in SAP-BPC NW.
and what are the steps for Planning
and what are the steps for Consolidation
Regards,
Setty

Hi,
1) Attributes describe master data like a customer. The country where the customer resides, the industry etc. describe and classify the customer. Attributes are not just the structure/metadata of the characteristics. They are also the content. The following table should visualize what i mean:
customer-no. | name
112 | mcpherson inc.
113 | donalds inc.
2) I think, you are asking about the laods from infopackage. We dont have types of infopackage. But we have one thing called Infopackage group, You can create the IPG with the selction of all infopackages in RSA1-Modelling Area to automate those loads automatically. That means it will trigger only those IP's which have been pooled up in that IGP...
Basically there are three types of loads in Infopackage
Full Upload: This will bring all the records in the BW irrespective of how many times you load.
Init Delta: In this you have 2 options: a) Init with data transfer and b) Init without data transfer. Init without data transfer will just setup your delta and when you do the delta load it will bring all the records. Init with data transfer is similar to the full upload. This brings all the records for the first time and will also setup the delta process. Once the Init is done; you have to do delta for all the subsequent loads.
Delta: This will bring only the changed / modified / added / deleted records from the source to BW.
Hope it helps..
Regards
Lavanya

What is the flow of FI ?

Similar Messages

Maybe you are looking for