Professional Documents
Culture Documents
SAP Handling Unit Management PDF
SAP Handling Unit Management PDF
management (HUM)
Document is useful for SAP MM/WM/SD
Consultants
G.V.SHIVAKKUMAR
6/16/2012
Venkatesansivakumar@yahoo.co.in
G.V.SHIVAKKUMAR
Handling Unit management (HUM)
I have used the Diagrams in Document Intro’. Reason..I hope it is useful for a person when he is a first
time Reader/ learner in HUM.
HU Overview
The SAP ERP system sees a handling unit as a physical unit that consists of the
packaging materials (load carrier / packaging material) and its goods. A handling unit is a
combination of materials and packaging materials. All the information contained in the
material items, such as batches and serial numbers, is available by way of the handling
units.
The handling unit in a non HU Storage Location differently from handling unit in HU
Storage Location means that there is no control over the packed units, in other words the
system does not control the inventory. It is mostly used there no need to keep packed
quantity in-house but only the need for shipping the goods wrapped in packages, the
handling units are then packed at the delivery area (it can have packing under other
packing which is called nested handling unit).
The handling unit in a HU Storage location means that there is control over the packed
units, in other words the system controls the inventory. It is mostly used when goods are
stored in a packed material like cartons, pallets, etc. The handling units can be nested
and the HU transactions allow the unpacking and packing activities as well as moving the
HU from one area to another.
The handling units can be proposed in a sales order and determined on the delivery
creation. The handling units can be also staged using Warehouse Management in process
manufacturing.
•Goods issues for the withdrawal of components. For production orders with many
components you can make the logistical processes considerably simpler. You can
withdraw components that are already being managed in HUs or first create the HU
when the components are picked.
•Goods receipts for materials produced. If you use make-to-stock production you can
handle partial quantities of stock individually with differently packaged handling units
(for example: packaging variations for different customer groups). Using handling units
serves to optimize logistical processes and does not influence the flow of capital in an
organization. This means that all goods movements continue to be posted to the
relevant production orders. If you use handling units, they offer you the following
advantages: •Carrying out goods movements is made simpler. •Material flows become
clearer and can be monitored or traced more easily. •Products can be individually
packaged, even in make-to-stock production.
•Goods receipts
•Goods issues
•Transfer postings
•Stock transfers
When you post a goods movement in a storage location that is subject to handling unit
management, the system creates a delivery. It does not create a material document. The
goods issue is not valuated until the delivery is posted in Shipping (also refer to Goods
Issue). Prerequisites:-Setting Up and Cancelling the HU Requirement in a Storage
Location. To set up or cancel the handling unit requirement in a storage location, all the
stocks in the storage location have to be posted out, so that the stock balances are zero
for all materials. This also applies to special stocks that are managed at storage location
level. After the handling unit requirement is changed, you can re-post the stocks to the
storage location. You can define the handling unit requirement in Customizing for
Handling Unit Management, in the step HU Requirement for Storage Locations and
Default Values for Deliveries.
•Plant data (sales organization, distribution channel, shipping point, and division)
•The Customer field in the central vendor master record, as the vendor for shipping is
also the customer
You can define the required plant data in Customizing for Handling Unit Management, in
the step HU Requirement for Storage Locations and Default Values for Deliveries.
Features
You can use all the functions of Inventory Management, with the exception of the
following:
•When goods are received for a purchase order, you cannot subsequently enter a freight
vendor that is different from the vendor. You can only enter a different freight vendor by
changing the relevant purchase order.
•When goods are received for a purchase order, you cannot create a purchase order
automatically, as goods movements in a storage location with handling unit requirement
are carried out using deliveries.
•Handling Unit Management is only supported for special stocks if the special stocks are
managed at storage location level.
If, in a storage location that is subject to handling unit management, you want to
increase or decrease the stock of a handling unit by transferring stock, you can define
another storage location as a partner storage location. The system then suggests this
G.V.SHIVAKKUMAR - SAP MM WM LE Consultant Email Venkatesansivakumar@yahoo.co.in
Page 6
Handling Unit management (HUM)
partner storage location any time you do not enter any other storage location. You
configure this in Customizing for Handling Unit Management, in the step HU Requirement
for Storage Locations and Default Values for Deliveries.
Object Reference for Handling Units:- it is useful for warehouse person to Identify where
the HU is used currently and to avoid the process errors. We can see the Object
reference in HU Monitor.
HU LABEL
HU in Mobile Data Entry- I have covered the information in My earlier document “ SAP WM -RF
Device management.
IM with WM
For your clear understanding SUM is a subdivision of storage Bin where stocks are stored with SU
number rather in quant number. The another advantage of SUM is, we can maintain two or more
different quants inside a SU.
Both SUM and HUM shares same identification number, whereas SUM features limited within the
warehouse, and HUM has its role outside the WMS.
HU is basically a material(s) which can be packed using packing material(s).
SU is defined for the purpose of handling and storing the material in Warehouse. you can have
full pallet, half pallet or pallets of different sizes and capacities.
Following are the differences i can think of.
Handling unit management can be used with or without WMS. But when you have WMS in place
you need SUM to process handling units.
SUM:
1. SUM can be controlled for each storage type and allows you through the use
of Sus to manage material quantities for each container or pallet as a self
contained unit within a storage type.
2. Certain storage functions such as mixed storage control, removal from
storage functions in bulk storage ,or capacity checks requires use of SUM in
the warehouse as prerequisite. SUM activated for following reasons
1. Movement of mixed pallets as a single unit within the warehouse.
2. Identification & management of materials using storage unit numbers
assigned internally or externally.
3. WM can communicate with fork lift control systems via interface without
having to maintain material data in the external system.
HUM:
1. HUM represents a packaging controlled logistics system in which all
movements are mapped through HU’s.
2. If we use HUM then you must use the GR process with inbound deliveries.
3. If we use HUM in connection with WM then we must activate storage unit
management for all storage types in which you want to store HU's.
4. During put away the system creates SU for the HU of the reference
document, e.g. inbound delivery. This SU has the same identification number
as its sister HU.
5. HUM must be activated for each plant/storage location combination.
6. HU itself is created in inbound delivery during packaging.
SAP HU Customizing
The settings for handling unit are relatively simple and just take few steps, the demand
for further use in HU like combination with warehouse , picking-HU, HU determination or
also aggregated functionalities increase the complexity level accordingly. Basically the
necessary conditions is to set a packaging material type and a material group for
packing and have it assigned to material of the packing type. Some further minor setting
and any packable material can be packed in it, detailed information is available in
creating a packing material wiki page.
HU Structure
The VEKP table (Handling Unit - Header Table) is the one which contain the identification
and main overall information of the HU, the details is found in the item level, there are in
the table besides the ones shown in the picture below the fields related to status, which
document the HU is assigned and document number which HU is assigned, those fields
are very important to determine the current status of the HU.
The VEPO table (Packing: Handling Unit Item (Contents)) is the one which contain the
that has either material or pack information (in case of a nested HU exists), it is the item
level. All the HU must be comprised of Header + Item levels.
HU creation summary
In this case the HU is created in ERP logistics directly in case where the packing occurs
before the delivery takes place; in this case it occurs on a HU managed storage
location hence the inventory of the HU is taken place in MM-IV-GF (storage location
inventory level). It can be done with only one transaction and it is required to have pre-
settings like material package created and storage location set as HUM and its partner
location pre-defined.
Instructions
The example below looks like very similar to the one for non HUM storage location. The
difference is to fill the partner storage location into storage location field and then fill the
HUM storage location into destination storage location field. Then a 311 material
movement is performed when it is saved.
Go to transaction HU02:
1. Go to tab “Pack material”;
2. Enter packaging material on the top section of the screen under the column
“Packaging Materials”;
G.V.SHIVAKKUMAR - SAP MM WM LE Consultant Email Venkatesansivakumar@yahoo.co.in
Page 14
Handling Unit management (HUM)
3. Press enter and a HU number is automatically generated and can be seen under
the “Handling Unit” column;
4. On the lower section of the screen, enter the material to be packed, the quantity to
be packed, the plant and the storage location. Here is the difference from non-HUM
storage location, the storage location MUST BE the partner of HUM one;
5. Enter the HUM storage location into Destination Storage Location field;
6. To pack the material onto the HU, select the material in the lower section of the
screen, select the HU just created in the top section of the screen and click on the pack
button (as indicated in the screenshot below);
7. Click the <save> button and the HU have been created. Notice that a material
document is also created.
HU creation summary
In this case the HU is created in ERP logistics directly in case where the packing occurs
before the delivery takes place, in this case it occurs on a non-HU managed storage
location hence the inventory of the HU is not taken place in MM-IV-GF (storage location
inventory level), it would only be part of inventory if storage location is set to HU
managed one. It can be done with only one transaction and it is required to have some
pre-settings like material package already created.
Instructions
The example below was done after some basic settings on the material and its package
material for that plant and storage location.
Go to transaction HU02:
1. Go to tab “Pack material”;
2. Enter packaging material on the top section of the screen under the column
“Packaging Materials”;
3. Press enter and a HU number is automatically generated and can be seen under
the “Handling Unit” column;
4. On the lower section of the screen, enter the material to be packed, the quantity to
be packed, the plant and the storage location. This plant and storage location should be
non HU managed;
5. To pack the material onto the HU, select the material in the lower section of the
screen, select the HU just created in the top section of the screen and click on the pack
button (as indicated in the screenshot below);
HU creation summary
In this case the HU is created in ERP logistics directly in case where the packing occurs
before the delivery takes place, in this case it occurs on a HU managed storage
location with Warehouse hence the inventory of the HU is taken place in MM-IV-GF
(storage location inventory level) and Warehouse level. It can be done with only one
transaction and it is required to have pre-settings like material package created and
storage location set as HUM and its partner location pre-defined.
Instructions
The example below looks like very similar to the one for HUM storage location. It is just
required that final HUM storage location is also WM managed. The warehouse details
about where stock was placed can be found in material document details that are
generated through HU02.
Go to transaction HU02:
1. Go to tab “Pack material”;
2. Enter packaging material on the top section of the screen under the column
“Packaging Materials”;
3. Press enter and a HU number is automatically generated and can be seen under
the “Handling Unit” column;
4. On the lower section of the screen, enter the material to be packed, the quantity to
be packed, the plant and the storage location. Here is the difference from non-HUM
storage location, the storage location MUST BE the partner of HUM one;
5. Enter the HUM/WM storage location into Destination Storage Location field;
6. To pack the material onto the HU, select the material in the lower section of the
screen, select the HU just created in the top section of the screen and click on the pack
button (as indicated in the screenshot below);
7. Click the <save> button and the HU have been created. Notice that a material
document is also created.
If you want to locate the just created stock in warehouse proceed as follow:
Go to transaction MB03:
1. Enter material document and material document year, depress <enter>;
2. Hit the destination item of the just created (double click);
3. Hit WM Details.. button, then you can check current information on storage type
and bin;
Go to transaction LS28:
1. Enter warehouse information just collected from MB03, depress <enter>;
2. Notice that HU are shown in Storage Unit field (it is how HU is called inside WM);
HU Main Operations
A handling unit can be monitored through the HUMO transaction which presents all the
handing unit information like status, document referenced, movement history as well as
HU further levels
content. The VLMOVE transaction is then used for the movements possible for any
handling unit and the packing/unpacking can be done through the delivery transactions
(inbound/outbound). A handling is mostly created through HU02 transaction.
For the individual document types: Inbound and outbound delivery, transfers,
material documents, and so on (HUIBD, HUOBD, HUTRA and so on);
Handling units are not included in document archiving for the delivery or the
transport. However, there is a report that archives handling units;
HU Transfer Summary
A known HU number is selected to be stored in a specific location; in this case it is from a
non-HU managed storage location into a HU managed storage location. The
goods in this case were already packed in the original location. Even though VLMOVE
does also some other processes like material to material and plant to plant it is not
covered in this specific article.
Instructions
The example below was done after having created some HUs of that material and packed
in a non-HUM storage location. So, basically the idea is to select it and inform the
destination data in that transaction, no delivery or posting change are created for the
311 movement, but a material document.
Go to transaction VLMOVE:
1. Enter 311 in process movement field;
2. Enter the destination plant and storage location value that it is expected to store
the HU;
4. Depress <enter>, notice that HU now shows in the bottom portion of the screen;
HU Transfer Summary
In this case a known HU number is selected to be stored in a specific location in this case
it is from a HU managed storage location into a non-HU managed storage
location. The goods in this case were already packed in the original location. Even
though HUMO does also some other process like In unrestricted-use stock, In inspection
stock, In blocked stock, they are not covered in this specific article.
Instructions
The example below was done after having created some HUs of that material and packed
in a non-HUM storage location. So, basically the idea is to select it and inform the
destination data in that transaction, no delivery nor posting change are created for the
311 movement, but a material document.
Go to transaction HUMO:
1. Enter a known HU number in Handing Unit field;
2. Depress F8 key;
4. Through menu Edit find the option to perform the transfer you wish to perform (in
this case a simple transfer between location);
step by step information of the instructions for MB1C and VL32N transactions which
perform the stock placement of material for HU managed location. It has screenshot
used in this example as well as hyperlinks to other forms of HU creation.
HU creation summary
In this case the HU is created in ERP logistics directly in case where the packing occurs
before the delivery takes place, in this case it occurs on a HU managed storage
location hence the inventory of the HU is not taken place in MM-IV-GF (storage location
inventory level)until it is packed. It needs to be done with assistances of two transactions
and it is required to have some pre-settings like material package already created and
storage location already set as HU managed.
Instructions
The example below was done after some basic settings on the material and its package
material for that plant and storage location.
Go to transaction MB1C:
1. Enter movement type 501 and plant/storage location to the HUM location, depress
<enter>;
2. Enter material and quantity to be received, depress <enter>;
3. Save it (notice that rather material document creation system creates a delivery
document).Notice that stock still does not present the quantity done in this process
(MMBE transaction).
Go to transaction VL32N:
1. Enter the delivery document just created from MB1C;
2. Go to pack screen and performing packing for the whole quantity in the delivery,
then save it;
3. Once delivery document status shows packing as completed (along any other
necessarry actions completed) you post PGR. Notice that stock now presents the
quantity done in this process (MMBE transaction);
HU creation summary
In this case the HU is created in ERP logistics directly in case where the packing occurs
before the delivery takes place, in this case it occurs on a HU managed storage
location hence the inventory of the HU is not taken place in MM-IV-GF (storage location
inventory level)until it is packed. It needs to be done with assistances of two transactions
and it is required to have some pre-settings like material package already created and
storage location already set as HU managed.
Instructions
The example below was done after some basic settings on the material and its package
material for that plant and storage location. It is also required that process has already
been initiated until step 2 of VL32N (check HU STOCK PLACEMENT)
Go to transaction LT03:
1. Enter delivery number and warehouse number then depress <enter>;
2. Click on button "Create trans. Order" and green arrow back;
Go to transaction LT12:
1. Enter Warehouse and TO number just created then depress <enter>;
2. Click on save the the TO number is confirmed;
The stock is already in warehouse, the process though is completed when inbound
delivery is PGR (VL32N) then inventory is completed.
HUM/WM location HU must be packed in WMS then goods issue afterwards through
delivery document.
Instructions
The example below was done after having the outbound delivery created in a plant and
storage location which is HUM and WM. So, basically the idea is to create a Transfer
Order in warehouse management system with an available HU and confirm it. It will allow
posting that packed quantity from the stock through outbound delivery document.
Go to transaction LT03:
1. Enter warehouse number and delivery number then depress <enter>;
2. Hit Create in Background button;
3. Check the selected HU in the bottom portion of the screen and Hit Save button;
Go to transaction LT12:
1. Enter warehouse number and TO number then depress <enter>;
2. Click on Save button;
The stock is no longer in warehouse, the goods issue process is completed, the HU has
PSTD status, the delivery is posted. Hence a material document related to the goods
issue created. That HU could be reversed by using the delivery document number in
VL09. Notice that document where HU is involved can only be reversed once. Some users
complain that STO cannot be reprocessed because HU needs reversal on both inbound
and outbound. It is a system restriction and in such case the operation needs to be done
in the opposite direction to release the HU for further operations.
HU issue summary
In this case the HU is picked in ERP logistics directly in case where the packing occurs
before the delivery takes place; in this case it occurs on a HU managed storage
location. The goods in this case are picked in the same quantity of HU. Even though it
is also possible to perform partial pickings from HUM which is called Pick-HU (LH01), it is
not covered in this specific article.
Instructions
The example below was done after having created some HUs of that material and packed
in a HUM storage location. So, basically the idea is to create outbound delivery without
G.V.SHIVAKKUMAR - SAP MM WM LE Consultant Email Venkatesansivakumar@yahoo.co.in
Page 47
Handling Unit management (HUM)
reference to a sales order and select an available HU from that plant and storage
location and post that packed quantity from the stock.
Go to transaction HUMO:
1. On Contents tab enter the material, plant and storage location you want to have
HU from;
2. On "Assignment to Objects" choose Handling units without object reference;
3. Hit Execute button or depress F8 key then just take note of HU number you wish to
issue;
Go to transaction VL01NO:
1. Enter related data on the first screen (remember that shipping point from same
plant/storage location from the HU chosen, hit execute button;
2. Fill the material also previously chosen along with its quantity, plant and storage
location, depress <enter>;
3. On the picking tab fill the pick quantity with the total quantity;
5. Fill in pack screen the HU you had previously chosen and depress <enter>, after
just hit Save button;
6. Now that Pack status is completed you have just to go ahead and Hit PGI button, if
you go to HUMO after that you can see that HU status is Posted.
The stock is no longer in warehouse, the goods issue process is completed, the HU has
PSTD status, the delivery is posted. Hence a material document related to the goods
issue created. That HU could be reversed by using the delivery document number in
VL09. Notice that document where HU is involved can only be reversed once. Some users
complain that STO cannot be reprocessed because HU needs reversal on both inbound
and outbound. It is a system restriction and in such case the operation needs to be done
in the opposite direction to release the HU for further operations.
Menu Path
G.V.SHIVAKKUMAR - SAP MM WM LE Consultant Email Venkatesansivakumar@yahoo.co.in
Page 53
Handling Unit management (HUM)
RF menu (LM00)
Outbound Process
Picking/Replenishment
When attempting to access transaction LM47 for picking nested handling units prior to
new screen definition, the following errors are raised:
An internal error has occurred
Logical screen number could not be found
EST
During the insert, warning may occur: 'Choose the key from the allowed namespace'.
Press enter to acknowledge.
Handling Unit
The SAP ERP system sees a handling unit as a physical unit that consists of the
packaging materials (load carrier / packaging material) and its goods. A handling unit is
a combination of materials and packaging materials. The handling units can be proposed
in a sales order and determined on the delivery creation. The handling units can be also
staged using Warehouse Management in process manufacturing.
Automatic Packing
The automatic packing functionalities are used in delivery transactions. (VL01N), WM
(Warehouse Management) and EWM (Extended Warehouse Management) transactions.
3. SPRO -> SAP Reference IMG -> Logistics - General -> Handling Unit
Management ->> Automatic packing -> Maintain Packing Transaction Profile
Transaction OVHU2
Packing transaction profile: e.g. 0002 Outbound delivery -> Detail
Determination procedure for packing instructions (V_CHUPDPARA1-
COND_SCHEME): e.g. 000001 pack in shipping set
4. SAP Menu -> Logistics -> Sales and Distribution -> Master Data ->
Agreements -> Pack -> Packing Instructions -> POP1 - Create
Transaction POP1
5. SAP Menu -> Logistics -> Sales and Distribution -> Master Data ->
Agreements -> Pack -> Packing Instructions -> Determination Records -> POF1
- Create
Transaction POF1
EAN128 Use
becoming more and more important. A common numbering standard that is defined by
the international standardization organizations (UCC, EAN International) forms the basis
for efficient processing in this field. These standards include the UCC/EAN128 and one of
its sub-components, the Serial Shipping Container Code (SSCC), which can be used to
identify the handling units that were shipped. Within the supply chain, handling unit data
can be transferred from one section to the next, for example, through EDI with EDIFACT
or EANCOM standards using the UCC/EAN128 and the SSCC. You can have the SSCCs
assigned as unique numbers as the handling unit is created. These numbers then serve
to identify and track the handling units. The SSCC and other parts of the UCC/EAN128
can be combined to form a valid concatenated bar code or they can be extracted from
such a bar code. The SSCC is created from its own number range object. Integration:-
The EAN128 numbering system is integrated in the packing function and the SSCC bar
code can be read whenever there is a delivery split.
Prerequisites:- Before you begin working with the EAN128 functions, you must acquire
the basic number ILN2 (ILN="international location number") from the UCC or EAN
International.
Features:-When you create a handling unit, you can have an SSCC assigned
automatically. This assignment is controlled by the packaging material type. The number
range used in this process is determined according to the following logic:
2. Warehouse number
3. Plant
4. Client
The SSCC can also be assigned externally by the user, in which case it is checked by the
system against an external number range that is found using the same logic. At the
same levels, the basic number of the ILN 2 that is required for generating the SSCC is
specified. You can also use the Output section of Handling Units Customizing to print an
EAN128 label. The structure of the bar code is controlled using a profile. Using this
profile, the system determines how many bar code lines are to be printed and where an
application identifier is to appear. The profile is assigned to an output type. You can
define different profiles for the different label types. These label types include: lower-
level HU (S - single label), HU containing only one material (M - main label), and HU
containing different materials (G - group label). You can control the form from the
standard output types in Customizing because the form and the profile are closely
related.
G.V.SHIVAKKUMAR - SAP MM WM LE Consultant Email Venkatesansivakumar@yahoo.co.in
Page 58
Handling Unit management (HUM)
Related OSS
I herewith attached the OSS Notes used during my past projects. I hope this will help the
consultants during their bug fix/issue resolution/Fix.
Dear Friends,
I hope all the topics in HUM is covered in this document. But again HU management is
vast one and it is integrating all IM/WM/PP/SD/QM/PM/CS. But it is more robust to cover
all the topics. I have covered Handling unit management concepts and how it is related
to Warehouse management. Also OSS notes shared in this document will help the
consultants. It is an process walk rather than configuration information.
Thanks for the continuous support. For this Handling unit management topics only I got
more than 100’s of mail form our friends...Thanks for showing interest and
encouragement given to me...
Regards,
G.V.Shivakkumar
venkatesansivakumar@yahoo.co.in
Or
SAP MM-WM
http://www.sapfunctional.com/WM/Configuration/Index.htm
http://www.sapfunctional.com/WM/WMQ1.htm
http://www.sapfunctional.com/MM/MMQ1.htm
http://www.mediafire.com/view/cxajoijh3j5s6es/Materials_Management_Step_by_Step_Configuration.docx
http://www.mediafire.com/view/33q7oslq3706oig/WM_Implementaion_Introduction.doc
http://www.mediafire.com/view/btrui8lnytcx8a6/WM_Training_documention_for_End_users.doc
http://www.mediafire.com/view/ym33706nci0iyv9/WM_Stock_Upload_Procedure.doc
http://www.mediafire.com/view/lcf45t12n4899nx/SAP_Workflow_for_MM_Purchase_order.docx
http://www.mediafire.com/view/au3y3bgas58m236/SAP_DECENTRALIZED_WAREHOUSE_SYSTEMS.docx
http://www.mediafire.com/view/03wud5d1nwjc56f/SAP_LEAN_WAREHOUSE_MANAEMENT.docx
http://www.mediafire.com/view/9kbas2mzygsn9b2/SAP_MM_Pricing_Procedure.docx
http://www.mediafire.com/view/n1w8zl1d7br5ea5/SAP_MM_BUSINESS_BLUE_PRINT_Sample.docx
http://www.mediafire.com/view/uujt3evdcyl69e2/Comparison_between_SAP_IM-_WM_–Lean_WM_–_DWM_–
_EWM.docx
http://www.mediafire.com/view/gq85534bj7a3lrz/Comparsion_between_SAP_WM_&_EWM.txt
SAP CIN
http://www.mediafire.com/view/twttbf5409s4zfr/MM_CIN_Configuration.doc
http://www.sapfunctional.com/MM/CIN/Index.htm
http://www.mediafire.com/view/hdfm84rmkq7h495/SAP_INTEGRATION_BETWEEN_MM+SD+PP.docx
http://www.mediafire.com/view/29trlg8qtn8z0nj/SAP_FI-MM_and_FI-SD_Integration.docx
SAP SD
http://www.mediafire.com/view/3cq2e2etbq0uty5/SD_Blue_Print_Document_Sample.docx
SAP PP
http://www.mediafire.com/view/jsxdahajsaizaz9/SAP_kanBan_Process.doc
http://www.mediafire.com/view/zteht2ulkb8x2y8/SAP_Production_Planning_overview_for_New_SAP_Consult
ants.docx
http://www.mediafire.com/view/jsxdahajsaizaz9/SAP_kanBan_Process.doc
http://www.mediafire.com/view/2lxa6weo8zcys17/Interfacing_with_SAP.doc
http://www.mediafire.com/view/nfyzuld416a1fco/SD_FLOW_&_FI_FLOW.docx
http://www.mediafire.com/view/svz777fpr8w0o2e/Systematic_Approach_to_Run_SAP_Implementation-
Support-Maintenance_Project.docx
Interfaces
http://www.mediafire.com/view/2lxa6weo8zcys17/Interfacing_with_SAP.doc
http://www.mediafire.com/view/pdb3ofaddcgccwv/SAP_LOGISTICS_EXECUTION-
_TRANSPORTATION_MANAGEMENT.doc
http://www.mediafire.com/view/3msem7578rcdecx/Batch_Management.doc
Regards,
G.V.Shivakkumar