RE: Difference between Storage location and warehouse

Hi All,
What is the difference between storage location and warehouse?

Hi,
First of all Storage Lcoation is part of Inventory Management.
Warehouse is part of Logistics Execution.
Storage location is part of SAPu2019s enterprise structure that holds the stock quantity
Option: To maintain a single storage bin for every material in every storage location
To simplify: To utilize a storage location as the u201Cstorage facilityu201D means that the materialu2019s actual bin location is not important, or that the material is located in a single bin throughout the storage.
Warehouse is part of SAPu2019s enterprise structure that holds the stock bin location
To simplify: When a warehouse (Warehouse Management) is utilized as a storage facility, a materialu2019s actual bin location is of great importance
Advantage: Track a materialu2019s changing bin location
Warehouse Management has greater applications for use in a storage facility
Disadvantage: More complexity and usually requires more data entry
Hope this helps.

Similar Messages

Difference between inventory management and warehouse management

can any body tell me the difference between inventory management and warehouse management i need atleast five differences

hi
1.
Processes in the area of Inventory Management address the recording and tracking of materials on a quantity and value basis. This includes planning, entry, and documentation of stock movements such as goods receipts, goods issues, physical stock transfers, and transfer postings as well as the performance of physical inventory (stocktaking).
Warehouse Management Processes cover warehouse-internal movements and storage of materials.
2.
SAP Warehouse Management allows you to manage your material flow, using advanced putaway and picking strategies. In the standard system, these strategies for putaway include random putaway (next empty bin), bulk storage, fixed bin, or addition to stock. The picking strategies include standard strategies first-in first-out (FIFO), last-in first-out (LIFO), picking by shelf life expiration date (SLED), or partial quantities first. For customer-specific strategies, solutions can be self-defined in user exits.
3.
While Inventory Management manages the stocks by quantity and value, the Warehouse Management component reflects the special structure of a warehouse, and monitors the allocation of the storage bins and any transfer transactions in the warehouse.
Reward points if helpful

DataSource - difference between ejb-location and location

Hi,
Does anyone know difference between ejb-location and location attribute specified in datasources.xml for an emulated datasource.
There are few connection leakage errors reported in log files though the connection and other database objects have been closed in finally block in all places.
So just wanted to find out whether specifying the same value for location as well as ejb-location is not the root cause of connection leakage errors.
Thanks in advance for any help.
Regards,
Smita

Smita,
Personally, I think you should make sure that all locations (in your "data-sources.xml" file) should be different -- although I can't tell you why.
According to the documentation, the "ejb-location" uses a connection pool and I exclusively use the "ejb-location".
Good Luck,
Avi.

Difference between Storage Grain and Query Grain

What is the difference between Storage Grain and Query Grain ?
In the query below:
Select quarter, YearAgoSales:
Query grain: quarter
Time Series grain : year
what is the Storage Grain ?
As mentioned in Help Guide, Storage Grain is "grain of the aggregate source".
Regards,

storage grain: by its name is the grain of your source.
query grain: by its name is the grain at which you define your query.
based on the example you mentioned:
Though you have a source at day grain, you are querying at quarter level (which corresponds to query grain)....
mark posts promptly
-bifacts
http://www.obinotes.com

Link between storage location and batch number to retrive the salk3 field

HI,
In my report i need to give the output as follows
For each lgort with related batch number we need to get the salk3.So i need to get a link between lgort , batch number to retrive the salk3.can any one give the tables from which i can get the link and retrive the data.
note: My report output should look like the fields lgort batch and unrestriced value of stock in tcode mb52.
subhashini.
Edited by: subhashinikb on Apr 1, 2011 9:38 PM

Hi,
In 2 steps, u can get the unrestricted stock value.
step1: Get material no (MATNR), plant (WERKS), batch (CHARG) and unrestricted stock (CLABS) from table MCHB by sending Storage location and batch number.
Step2: Get standard price STPRS from table MBEW based on condition where MATNR = MCHB-MATNR, BWKEY = MCHB-WERKS and BWTAR = MCHB-CHARG.
unrestricted value in MB52 will be (MCHB-STPRS) * (MCHB-CLABS).

Stock transport order between storage locations and assignment category type E not in MRP

Hello Gurus,
I have a stock transport order between 2 storage location which belongs to the same plant. Besides the stock transport order is allocated to a sales order (account assigment category E). When I run the MD03, the system take into account the quantity of the stock transport order as a future entry and this is wrong. I need that the MRP has not into account the stock transport order as an entry.
As an important information, If I modify the stock transport order removing the account asignment category E (sales order), then the MRP doesn't take into account it, so this is correct.
Could anybody tell me how to get it?
Thanks in advanced.

Laura,
It is normal that MRP will consider an STO as a receipt element; this is basic planning. It is unclear to me why you think you do not want it to do so, but I will assume you have some logical reason.
Contrary to what some others may have suggested, changing the scope of check for availability checking has no effect on which elements are considered for MRP. MRP is a completely separate functionality from Availability Check.
For Location > Location STOs (within a plant), then, you normally have the receipt element of the STO in the destination storage location, and the requirements element of an equal amount in the source storage location. Net of these two elements is zero, unless you have already issued the STO at the source location.
Changing the Account assignment from "E" means that the STO will not be relevant for your Sales order (in other words, when you receive this STO into the destination storage location, it cannot be used for your sales order). In a general MTO scenario, it also means that the proceeds of this STO (the stock you received) cannot be used for ANY sales orders.
One way that some people make an STO 'not relevant' for MRP is to alter the destination storage location such that it is not relevant for MRP. You can change the MRP relevancy of the storage location in MM02 > MRP4 tab
Best Regards,
DB49

Stock transfer between storage locations and lead time

Hello,
We use stock transfer orders between different storage locations. Is it possible to maintain the transport lead time between storage locations somewhere or do in need to use routes and scheduling?
rgsd
GAR

Hi,
Try using movement type 313 and 315
313 -- Transfer posting SL to SL --- Remove from issuing SL
315 -- Transfer posting SL to SL -- Placing in Receiving SL
Regards

Potential Versioning Differences Between Storage Server and Grid Infrastructure/DB

Hello.
While awaiting my MOS CSI access to be approved For Exadata HW issues so I can open an SR, I have a question. We are about to apply QFSDP for BP 22 on one of our full RACK X3 Exadta servers. Currently, the Grid Infrastructure (GI)/DB SW is at 11.2.0.3.0 and teh storage SW is at 11.2.3.2. Our last BP was 19. BEFORE we apply the BP 22, we want to upgrade the clusterware to 12c - but not the DB (that will come later). This is a high level question which I have discussed with several Oracle techs, but wanted to see what the experience/opinion is while I await access to my CSI. Can you have your Grid Infrastructure (GI) running at a higher version than that of your your storage server? The tech I spoke to said that all GI/DB SW should be at a version that is NO GREATER than that of the storage server - meaning a 12c version of the GI would not be compatible with a lowere version of the storage server. Thank you in advacne for any guidance.
Regards,
Matt

Hi Matt,
Seems you want to do a lot in one go here.
Maybe you should look at Doc ID 888828.1, Doc ID 1537407.1 and Doc ID 1373255.1 for a start.
For 12c (grid and rdbms) on Exadata it is recommended to upgrade your FW to 12.1.1.1.0 first.
My advice would be to patch up 11g to BP22 and when done start planning the 12c upgrade (keeping the 11g dbhome).
Regards,
Tycho

Storage location and post.chge storage location not in the same warehouse

Hi All,
We have HU managed Storage Location, and in this Storage Location we have SUT managed Warehouse, Now while Goods Receipt we have to create inbound delivery, which is working fine and i can see my stock in Goods receipt area,, later on whicle creating Transfer Order to putaway in a bin i have a error message "Storage location and post.chge storage location not in the same warehouse" please help me with this error message. Thank you for all your inputs.
Regards
Samuel

Hi Nagesh,
Thank you for the input. I am receiving Stock from vendor and while creating Inbound delivery i created the Handling Unit and also packed it and i could also post it (PG Receipt). Now when i am creating TO i have that error message. The Storage Location where i am receiving is 9001and i have also maintained the partner Storage location,,, its like this Plant(1000)-SLoc(9001)-Partner SLoc(9002).... now the Storage Location 9002 is not HU managed,, the reason i gave this Storage location is, initially i gave 9001, but system said "Storage Location 9001 and 9001 must have different management systems". So now kindly tell me what is the purpose of the partner Storage location and which storage location should i give, as my partner Storage location across "1000-9001-????" thank you again for ur inputs.
Regards,
Samuel

Differences between oracle 10gr2 and 11gr2 warehouse bulider

Hi All,
Could you please let me know the main differences between Oracle 10gr2 and Oracle 11gR2 warehouse builder.
Also , it would be great if anyone point me to the document where i can see the major differences.
Thanks,
Naveen.

Hi Naveen,
The major difference between OWB10gR2 and 11gR2 is the target RDBMS.
In 10gR2 you have to use ORACLE as your target RDBMS (unless you are going for DB Gateways, that is a complete different story).
Where as in 11gR2 allows you to use any RDBMS as your target system . This is achieved by Code-Template mapping.
All is needed is that proper jdbc driver for the target system.
Also 11gR2 supports OBIEE RPD creation and etc.
http://blogs.oracle.com/warehousebuilder/2009/09/oracle_warehouse_builder_11gr2.html
http://www.rittmanmead.com/2009/09/a-look-at-the-new-features-in-owb11gr2/
http://www.oracle.com/technetwork/developer-tools/warehouse/owb-11gr2-new-features-summary-129693.pdf
Thanks,
Sutirtha

What is the difference between ECC 5 and ECC 6.0

Dear Experts,
Can any one tell me in detail the difference between SAP R/3 versions ECC 5 and ECC 6 functionality wise in MM mdoule?
To be specific what are the new features in MM being added in ECC 6.0 when compared with ECC 5.
Request your help in this regard.
Rgds,
Uzair
Edited by: Mohd Uzair Hussain on Jul 23, 2008 5:35 PM

Hi,
Refer following link;
[SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
- Goods receipt
- Goods issue
- Transfer posting
- Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
- To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
- Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
- Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
- Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
- 107: Goods receipt to valuated goods receipt blocked stock
- 109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location

Transfer posting between storage location

Hi
2 questions: we are going to create a new storage location to make material movements:
1- We have to move stock between storage location.
Storage A(new): without WM
Storage B: under WM.
We would like to know wich is the best practice to do the transfer: MB1B? 301/311 movement type?
2 - If we decided to create a new storage location with WM. Wich are the recomendations or the points we have to consider:
Under the same Warehouse numer? A knew storage type? Wich are the activities in SPRo?
Thanks in advance for the help
Regards
Enzo

http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/2b90dc43ad11d189410000e829fbbd/frameset.htm
If it is the same physical Warehouse you could use the same Warehouse, otherwise a new or no Warehouse.
If the Storage Locations are near by and stock doesn't cross public roads and it's manually initiated, suggest just use a one step as it's the simplest process.
If there's a significant distance but on-site use two-step or if stock transferred by public roads, use STO.

Replenishment between Storage Location with MRP Planning

Dear PP Gurus,
I need you expertise on the below question.
I have a plant with multiple Storage Locations. One Storage Location is Main Warehouse and another ilocation s External Warehouse (3PL) where excess stock are kept due to storage capacity in the Main Warehouse.
Now the requirement is replenish the stock to Main Warehouse from the External Warehouse with Stock Transfer using MRP trigger the Stock Transfer.
I know the setting in MRP 4 View in the material master, the Indicator to set to 2, maintain a reoder point in the Sloc: 1200 and Replenishment Qty: 1500 and Special Procurement Type: (what should be the setting)
My question is where to set the target Sloc and source Sloc, then only system will trigger the replenishment Stock Transfer?
The storage location which is plan separately, will have a different segment. Therefore, in terms of the availability check for the Sales Order it will consider as normal based on the scope of check.
Appreciate the reply
Thanks & Regards
Pooja

Dear ,
1.You need to set up the MRP for Plant with group of storage location and run MRP-MD01 .You can try SCOPE of planning -OM0E.
As an information : In standard MRP I, f you have several storage location for your plant, you cannot plan for them separately unless you assign them to a separate MRP area.If a storage location (alone) is assigned to an MRP area, it means you wan to plan for it separately. If several storage locations are assigned to an MRP area (or let's say to a plant), it means you want to plan using all of them - and you cannot choose only one and plan for it (you can exclude a SLoc from planning w/o assigning it to MRP area).
2.Find steps for config for activating Sloc to Sloc transfer within plant using STO : -
follow path: SPRO--> Materials Management -->Purchasing -->Purchase Order -->Set up Stock Transport Order -->Set Up Stock Transfer Between Storage Locations
1. Activate Stock Transfer Between Storage Locations
2. Assign Delivery Type and Checking Rule According to Storage Location
purchase document category 'F' , here use PO type UB, supplying plant, issue sloc and delivery type , (prefer to create new delivery type by copying delivery type 'NL' replenish delivery
3. Define Shipping Data for Stock Transfers Between Storage Locations
for plant defind sales org and distribution chenal and devision
select the pline and go to sloc
assign there customer (created for sloc)
4. Define Rule for Determination of Shipping Point
for newly created delivery type set L storage location specific shiping poing determination
5. Assign Shipping Points According to Storage Location, assign her sloc based shiping poing determination
at last when you will create PO put issue storage location, system will determine shiping data based on config done.
after this process will be same as STO plant to plant using shiping.
You will need to mention the issuing storage location during posting the delivery,
ie, ME21N - Create STO
VL10B - Create Delivery
VL02N - Post Goods issue - here you will need to mention the issuing storage location
Refer : STO process -Std in SAP
Hope it is clear to you .
Regards
JH
Edited by: Jiaul Haque on Jul 7, 2010 10:23 AM

Difference between Stock transfer and transfer posting

I am little confused about the difference between stock transfer and transfer posting. Please clarify
<<Locked - reason: failed to search before posting question>>
Edited by: Csaba Szommer on Feb 9, 2011 9:10 AM

Hello,
Transfer posting may involve or not involve the physical goods transfer. In the system you might do transfer posting from quality to unrestricted, or from one store location to another.
In transfer posting you remove and or replace materials from storage in one storage location and place them in another storage location.
That transction code you use for transfer posting MB1B with following movement types may be used
301, 303,305,311,411,309.
301 is Stock Transfer Between Plants in One Step
303 & 305 : Stock Transfer Between Plants in Two Steps
In stock transfer, it always involves physical movement of goods, like transfer between plants under same company code or different company codes.
Following types are possible with STO's
Stock Transport Order Without Delivery
Stock Transport Order with Delivery via Shipping
Stock Transport Order with Delivery and Billing Document/Invoice
http://help.sap.com/saphelp_470/helpdata/en/4d/2b90dc43ad11d189410000e829fbbd/content.htm
Please go through attach SAP document
BR,
Tushar

Difference between Master Idoc and Communication Idoc.

Can anyone list out the difference between Master Idoc and Communication Idoc?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
Layout of an IDoc control record
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

RE: Difference between Storage location and warehouse

Similar Messages

Maybe you are looking for