Logistik + Informatik GmbH Neustdter Str. 21 D - 92711 Parkstein Tel.: +49 / (0) 96 02 / 6 00 - 0 Fax.: +49 / (0) 96 02 / 6 00 - 2 11 Email: INFO@WITRON.

DE

M.O.B.-to-R/3 - Documentation
Special features for Tetra Pak

Version: 1.0, Date: 17th of June, 2008 Author: Jrg Holzpfel

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

Copyright. All rights reserved by WITRON. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission in writing of WITRON. Subject to alteration. WITRON reserves the right to change or correct the product specifications described in this documentation at any time. The programs described or mentioned in this document are conceded due to a license agreement and may be used or copied only in accordance with the regulations agreed on in the license contract. All company and/or product names are trademarks and/or registered trademarks of the respective holders. 2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

History Date 30.05.08

Version 1.0

ID hoj

Description New document

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

Table of contents 1 ....................................................................................... Data exchange with SAP 1

1.1 ...................................................... Transfer order creation initiated on R/3 side 1 1.2 ................................................... Transfer order creation initiated on MOB side 2 1.2.1 ................................................................................................ General relocation 2 1.2.2 ...................................................................Box relocation, Additional Materials 2 1.2.3 ..................................................................................... Inbound Finished Goods 3 1.2.4 ................................................................ Replenishment for production supply 3 1.3 ...............................................................................Cancellation of transfer orders 3 1.4 ..........Transfer order state synchronization between MOB-to-R/3 and SAP 3 1.5 ............................................................................................. Cancellation of picking 4 1.6 .............................................................................................................. Goods receipt 4 1.6.1 ...................................................................... Goods receipt for purchase order 4 1.6.2 .............................................................. Goods receipt for shipping notification 4 1.6.3 .................................................................... Goods receipt for production order 5 1.7 .............................................................................................. Picking for cost center 5 1.8 ....................................................................... Goods issue to maintenance order 5 1.9 ......................................................................................Goods issue to cost center 5 1.10 ...............................................................................................Change of stock type 6 1.11 ............................................................................................................... Bin blocking 6 1.12 ................................................................................................... Bin and SU inquiry 6 1.13 .............................................................................................................. Stock inquiry 6 1.14 ........................................................................................................ Initial stock take 7 1.14.1 .......................................................................................... (Old) online versions 7 1.14.2 ..................................................................................... (Newer) offline versions 7 1.15 ................................................................................................... Inventory counting 7

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

Data exchange with SAP

MOB-to-R/3 uses two fundamentally different ways of data exchange with SAP: Exchange of IDOCs (= Intermediate Documents) is used whenever data have to be certainly transferred to the partner system, but without the requirement of an immediate feedback about the success of the transfer. Processes running in the background guarantee that once created IDOCs will reach the partner system also in case of connection breakings. The used technique is TRFC (= Transactional Remote Function Call): A so-called TID (= Transaction ID) uniquely identifies every package of IDOCs to be transferred and thus guarantees that every IDOC package is processed by the partner system exactly one time. The call of function modules in SAP by SRFC (= Synchronous Remote Function Call) is used whenever a direct data exchange with SAP is required or if the result of data processing in SAP is immediately required in MOB. The following sections describe, how data exchange between MOB-to-R/3 and SAP is implemented for the different functionalities in Tetra Paks version of MOB-to-R/3.

1.1

Transfer order creation initiated on R/3 side

Transfer order IDOCs WMTOID01 are created in SAP sent to MOB. Transfer orders are posted into the TO shared memory after successful processing by processes arfc_rcvd and mob_rcvd. Dialogues 11, 41, 43, 44 and 74 are working with these transfer orders. These dialogues create confirmation IDOCs WMTCID01, which will be sent back to R/3 by the arfc_sndd process. In case of picking from a bulk storage with dialogue 74, the full information about boxes, which have been picked from certain storage units, is sent to R/3 within a Tetra Pak specific modification of IDOC WMTCID01: The type of the modified IDOC is ZMTCID01. At least for dialogues 11, 41 and 74, there is also a bulk storage picking case: Information about the currently picked storage unit is downloaded from R/3 by an SRFC call of function module Z_STORAGE_UNIT_2_5. Some of the mentioned dialogues allow a confirmation with a changed destination bin. A function module Z_TO_CHECK_STORAGE_BIN is called by SRFC to check, if the changed destination bin is allowed for the transfer order. The transfer order confirmation IDOC WMTCID01 provides a field for the changed destination bin.

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

1.2

Transfer order creation initiated on MOB side

Dialogues 26, 27, 72, 73 Different function modules, called by SRFC, are used to ask for the creation of special transfer orders. The resulting transfer orders are immediately returned by the SRFC. But every transfer order generation results additionally in the creation of a WMTOID01 IDOC, so MOB receives the same transfer order twice, one time by the SRFC, one time as IDOC, but posts it only one time into the shared memory (doesnt matter, if SRFC or IDOC is faster!) Transfer order confirmation is normally performed with IDOCs (see above)

1.2.1

General relocation
Dialogue 26 Function module Z_TA_RELOCATION_2_5 is called twice during every successful relocation with dialogue 26: At the first time only to check if the specified storage unit or quant may be removed from its current source bin, at the second time to check if it may be moved to the entered new destination bin and to get the relocation transfer order created. The import parameter I_KENNZ of function module Z_TA_RELOCATION_2_5 is used to distinguish the four cases to call the function module: I_KENNZ = L Used for source bin check, if the number of the SU to be removed is specified I_KENNZ = A Used for source bin check, if the quant to be removed is specified by source storage type, source storage bin, material number, batch and quantity. I_KENNZ = S Used for destination bin check and transfer order creation, if the number of the SU to be moved is specified I_KENNZ = E Used for destination bin check and transfer order creation, , if the quant to be moved is specified by source storage type, source storage bin, material number, batch and quantity.

1.2.2

Box relocation, Additional Materials

Dialogue 27 Function module Z_BIN_AND_SU_INFO is used to get information about available quants on the source storage bin. Function module Z_TA_RELOCATION_2_6 is used to get the relocation transfer created to move a list of quants to the destination storage bin.

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

1.2.3

Inbound Finished Goods

Dialogue 72 Function module Z_SU_MOVE_2_5 is used to get a relocation transfer order by one single step. In many cases the user might need to change the destination bin proposed by the created transfer order. Function module Z_TO_CHECK_STORAGE_BIN would then be used to check if this changed destination bin is a valid alternative for the original destination bin.

1.2.4

Replenishment for production supply

Dialogue 73 This dialogue uses function module Z_TA_RELOCATION_2_5 in a similar way as dialogue 26, but only with I_KENNZ=L or I_KENNZ=S. Function module Z_STORAGE_UNIT_2_5 is used to check if the SU contains a material which may be moved by this dialogue.

1.3

Cancellation of transfer orders

If someone tries to cancel a transfer order on R/3 side, a cancellation request IDOC WMCAID01 will be created and sent to MOB. Process mob_rcvd checks in the background (no dialogue involved), if the transfer order is still cancellable. Depending on that, an IDOC WMCAID01 with a positive or negative answer to the cancellation request will be created and sent back to R/3.

1.4

Transfer order state synchronization between MOB-to-R/3 and SAP

Background process mob_tar3sync searches all currently unconfirmed transfer order items in MOB and calls function module Z_TO_CONFIRM_CHECK to get the confirmation state of these items in SAP (One call of Z_TO_CONFIRM_CHECK can check the state of multiple TO items). If an item is already confirmed in SAP but not yet in MOB, then it automatically gets the state Confirmed also in MOB.

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

1.5

Cancellation of picking
Dialogue 83 A function module Z_DELIVERY_SU_TP is called to check, if the picking of a specified storage unit for a specified delivery can be cancelled. If the cancellation is possible, then function module Z_CALL_LT0G_TP is called to get a transfer order created to move the storage unit back to a specified storage bin in the warehouse. This transfer order will be confirmed after successful working by sending an IDOC WMTCID01 to SAP.

1.6

Goods receipt
Different function modules, called by SRFC, are used to download purchase order or production order information. Goods receipt posting is also performed by an SRFC call of a function module. A successful goods receipt posting normally results in the creation of an inbound transfer order. IDOCs WMTCID01 are created during the confirmation of these transfer orders and sent back to R/3 by the arfc_sndd process.

1.6.1

Goods receipt for purchase order

Dialogues 71, 75, 81 Function module Z_GOODSRECEIPT_2_5_BATCH_CHANGE (a modification of the formerly used Z_GOODSRECEIPT_2_5) is used to download the purchase order including a complete purchase order item list. If a custom declaration number has been entered, then this number would be checked for validity by function module Z_VALIDATE_CD_NUMBER. Function module Z_CREATE_GM_AND_TO is used to post the goods receipt and to get an inbound transfer order created.

1.6.2

Goods receipt for shipping notification

Dialogue 71 Function module Z_LOAD_SN_2_5_TP is used to download the shipping notification. If a custom declaration number has been entered, then this number would be checked for validity by function module Z_VALIDATE_CD_NUMBER. Function module Z_CREATE_GM_AND_TO is used to post the goods receipt and to get an inbound transfer order created

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

1.6.3

Goods receipt for production order

Dialogue 85 Function module /TPISP/YM_DOWNLOAD_DATA_TO_PO is used to download the production order information about a storage unit. Function module /TPISP/YM_BOOK_MVMNT_CREATE_TO is then used to get an inbound transfer order created for the storage unit.

1.7

Picking for cost center

Dialogue 76 Function module Z_STORAGE_UNIT_2_5 is called to download information about a storage unit to be picked. The material on the storage has to be checked if it is allowed to be picked with this dialogue. Function module Z_GI_TO_COST_CENTRE_TP is then called to post the goods issue for the storage unit and to get a transfer order created. The transfer order will be confirmed after successful working by sending an IDOC WMTCID01 to SAP.

1.8

Goods issue to maintenance order

Dialogue 86 Material data for a selected maintenance order are downloaded from SAP by call of function module /TPISP/YM_DOWNLOAD_MAINTORDER. One of the downloaded materials is selected and a further function module /TPISP/YM_DOWNLOAD_MAINTQUANT is called to download possible quants for the selected material. The goods issue for a selected quant to the selected maintenance order is then booked by SRFC call of function module /TPISP/YM_CREATE_GM_TO_MAINT. This function module returns a transfer order which will be confirmed after successful working by sending an IDOC WMTCID01 to SAP.

1.9

Goods issue to cost center

Dialogue 87 Quants for a selected storage bin are downloaded by SRFC call of function module /TPISP/YM_DOWNLOAD_COSTCENTER. The goods issue for a selected quant to a selected cost center is then booked by SRFC call of function module /TPISP/YM_CREATE_GM_TO_COSTC. This function module returns a transfer order which will be confirmed after successful working by sending an IDOC WMTCID01 to SAP.

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

1.10 Change of stock type

Dialogue 77 The current stock type of a storage unit is downloaded with function module Z_STORAGE_UNIT_2_5. Function module Z_CHANGE_STOCK_TYPE_TP is called to change the stock type of the storage unit.

1.11 Bin blocking

Dialogue 61 Dialogue 61 (may be called within other dialogues by function key) creates IDOCs WMBIID01 with blocking or unblocking information. They are sent to R/3 by the arfc_sndd process.

1.12 Bin and SU inquiry

Dialogues 63 and 68 Function module Z_BIN_AND_SU_INFO is called to get information about a specified storage bin (dialogue 63) or a specified storage unit (dialogue 68). The function module returns a list of quants and additional information about the storage unit(s) where the quants are assigned to.. Function module Z_TA_RELOCATION_2_5 would be called if the user would decide to relocate a single quant or a complete storage unit. The relocation would work in the same way as the second step of dialogue 26 (see above).

1.13 Stock inquiry

Dialogue 67 A list of available quants for a specified material number and a list of specified storage types is downloaded from SAP by call of function module Z_FIFO_STOCK_TP_ISP.

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein

1.14 Initial stock take

1.14.1 (Old) online versions
Dialogues 78, 79 The results of the initial stock take are written into IDOCs: Goods movement IDOCs WMMBID01 are created to post the taken stock into SAP. Transfer order IDOCs WMTOID01 are created to post quantities of specified materials to specified storage bins in the warehouse. These IDOCs will be sent to R/3 by the arfc_sndd process. The transfer orders created by the WMTOID01 IDOCs are automatically confirmed in R/3.

1.14.2 (Newer) offline versions

Dialogues 82, 84 The results of the initial stock take are written into files on the MOB server. The content of these files is transferred to SAP by a program, which is not part of MOB-to-R/3.

1.15 Inventory counting

Dialogue 05 Inventory counting documents are created on R/3 side and sent to MOB as IDOCs WMIVID01. The documents are posted into the inventory document shared memory after successful processing by processes arfc_rcvd and mob_rcvd. Dialogue 05 is creating IDOCs WMIVID01 with counting results. These IDOCs will be sent back to R/3 by the arfc_sndd process. Similar to picking (see above) there is also a bulk storage case with the requirement to download information about the currently counted storage unit by call of function module Z_STORAGE_UNIT_2_5.

M.O.B.-to-R/3 - Documentation, special features for Tetra Pak

2008 WITRON Logistik + Informatik GmbH, D-92711 Parkstein