KANBAN Indicator

Hi,
I am trying to create a control cycle for a KANBAN scheduling agreement in transaction PK01.
I get the error - Scheduling agreement item has no kanban indicator or an incorrect one.
Can anyone tell me where can I set this indicator?
Thank you.
Would be glad to reward helpful answers.

Hi Krishna,
Thank you for your answer.
But aren't JIT and KANBAN different things?
When I opened the long text for the error message I am getting in PK01, it said that you have to set the KANBAN indicator to X for the item in the scheduling agreement.
As per my understanding, JIT is a different concept.

Similar Messages

Is there a procedure to auto populate shipping instructions on Kanban STOs?

Hello,
The scenario is this:
- intra-company STO (does not cross borders, no billing), type UB, created via Kanban when the bin is emptied
- for this organization, type UB STOs also originate from other sources (ie, conversion from Purchase Reqs), not just originating from Kanban; although for a single material within a plant, Kanban is the method and UB STO is the replenishment strategy
- Shipping instructions (on the Delivery Line Item tab) are a required field when UB STO is created directly, but via Kanban background process the STO is saved successfully without shipping instructions (I find this interesting). This is not a text for shipping instructions, it's the element EVERS, field name EVERS in structure MEP01313.
The problem is this:
- the user (in this case the planner) must go in to manually add the shipping instructions on the Delivery Line Item tab prior to SAP allowing delivery document creation & shipment activities. this manual intervention by the user is unacceptable to the business.
The desired solution from the business is this:
- the business has specified a default shipping instruction that they want (it is configured and ready to go)
Steps we've taken to resolve:
-I first thought of using a purchasing info record. But we cannot use a purchasing info record to default the shipping instructions because this STO is using SUPPLYING PLANT and not vendor as the relationship.
-Then, I thought about maintaining shipping instructions on the purchasing view material master record, but the requirement is to only default these shipping instructions when they originate from Kanban and when the STO type = UB. So I thought it was too broad because it could impact other purchasing functions for the same material, plus the info record doesn't work for supplying plant.
-Now I am thinking about a procedure of some sort to configure to find the correct shipping instructions when material master + STO data meet certain characteristics. Is there such a thing?
-Another option would be a user exit available in the STO to do a check for Kanban indicator and STO type and then to choose the desired shipping condition, but this doesn't seem as elegant as other potential options, and seems restrictive (ie, hard-coding the key for the desired shipping instructions or building a ztable with combinations of STO attributes and desired shipping condition, which requires maintenance).
-Finally, it seems odd that the background creation of the STO via Kanban doesn't trigger a hard error when it checks the document for completeness, rather than saving and getting a document # even though the document is missing a required field. This seems to point to STO user exit as a way to fix this problem.
Your thoughts on the assumptions we've made and the potential resolutions are greatly appreciated.
Rebecca
Edited by: Rebecca Slomski on Oct 8, 2008 7:37 PM

Answered my own question. This may help someone, so here is the answer for version 4.6.
The way to automatically default shipping instructions when the STO uses "SUPPLYING PLANT" instead of vendor is to first configure a purchasing value key that contains the shipping instructions. The path is: IMG>Materials Management>Purchasing>Material Master>Define Purchasing Value Keys.
Then, the material master record must be updated on the Purchasing View with the new purchasing value key.
Cautions to this approach:
1. Even though this is on the Purchasing View, purchasing value key is on the MARA table, so it is not a plant-specific material master setting. One purchasing value key per material master record.
2. The purchasing value key contains settings for reminders and over/under-delivery tolerance percentages. This is interconnected with the choice of shipping instructions. Be sure that the purchasing value key is configured to meet the wide variety of planning needs that could exist at multiple locations where the material is used.
3. Some of the above considerations are mediated by the fact that the material master purchasing value key is over-ridden by specific information contained on a purchasing info record or a contract.

KANBAN with Quota arrangement

Dear Guru,
Ist possible to use Quota arrangement in KANBAN external Procurement (Scheduling Agreement)?
If so, please advice me how to do it... i am new to KANBAN.
Regards,
Senthil

Hi Kumara,
As per my knowledge Quota Arrangement is not possible to use in KANBAN with Schedulling Agreement.
However pls find below the process steps for KANBAN WITH SCHEDULING AGREEMENT:
You can carry out KANBAN with Replenishment Strategy- External Procurement in following two ways :
1.     External procurement from Vendor to Main Stores:
Basic rules and Prerequisites:
u2022     MRP type should be u2018NDu2019 in MRP1 view of material master.
u2022     Availability check should be u201CKPu201D in MRP3 view of material master.
u2022     Material received from vendor is directly posted to unrestricted stock. Inspection at vendors place or vendoru2019s process control to ensure rejection free material. Inspection set up in Material master should be inactive.
u2022     Backflush is not required and Material is issued against a Pick List for Production Order.
Process steps:
1.     Create supply area for Main stores. TC: PK05
2.     If required, extend the material to main storage location. TC: MMSC
3.     Make the necessary changes in the material master as explained above.
4.     Create scheduling agreement. Put kanban indicator (X) in the additional data of item.
5.     Create Kanban control cycle. TC:PKMC
6.     Print the barcode. TC:PK17
7.     Set the kanban status to EMPTY by scanning the barcode. TC: PKBC. A Schedule line will be generated for the supply of material to main stores.
8.     View the demand source view. TC: PK13n
9.     When the material is received at Gate, perform goods receipt into blocked stock (movement type 103). TC: MIGO
10.     Once the material reaches Main stores scan the barcode to FULL. TC: PKBC (At the background GR with 105 movement will happen).
2.     External procurement from Vendor directly to shop:
Basic rules and Prerequisites:
u2022     MRP type should be u2018NDu2019 in MRP1 view of material master.
u2022     Availability check should be u201CKPu201D in MRP3 view of material master.
u2022     Backflush indicator is must. It can be defined in the routing or in the material master itself. If Backflush indicator is set in the material master, then the material will be backflushed through out the plant (Material issue not required against production order). However if you want the material to be backflushed only when it is used for certain products, then Backflush indicator should be set in the routing ( in the component allocation against operations).
u2022     Confirmation should be done for each operation in the production order either individually (CO11n) or collectively (CO15). Confirmation posts goods issue of components (relevant to confirmed operation/s) to production order
u2022     Maintain KN01 storage location in the field - production storage location of MRP2 view in the material master. Back flushing will take place from this location. Field - Storage location for external procurement should be KN01 in the material master.
u2022     Material received from vendor is directly posted to unrestricted stock. Inspection at vendors place or vendoru2019s process control to ensure rejection free material. Inspection set up in Material master should be inactive.
Process steps:
1.     Create supply area for kanban stores (KN01). TC: PK05
2.     Extend the material to Kanban storage location. TC: MMSC
3.     Make the necessary changes in the material master as explained above.
4.     Create scheduling agreement. Put kanban indicator (X) in the additional data of item.
5.     Create Kanban control cycle. TC:PKMC
6.     Print the barcode. TC:PK17
7.     Set the kanban status to EMPTY by scanning the barcode. TC: PKBC. A Schedule line will be generated for the supply of material to kanban store.
8.     View the demand source view. TC: PK13n
9.     When the material is received at Gate, perform goods receipt into blocked stock (movement type 103). TC: MIGO
10.     Once the material reaches shop, scan the barcode to FULL. TC: PKBC (At the background GR with 105 movement will happen).
Hope this helps.
Revert if any doubt and reward points if useful.
Regards,
Tejas

Kanban

Hello
I am working on KANBAN process and replenishment strategy as Planned order with MRP.
When i trigger the KANBAN card planned order is created.That will be viewed in the MD04
So my problem is i am not able diff between MRP run planned order and KANBAN triggered planned order.
EG: MRP triggered planned order as 1000000/Stck
KANBAN triggered planned order as 500000/Stck.
So is their any to change the suffixes of planned order number(Stck)

Hi
Check in the planned order, there would be a kanban indicator which would be automatically ticked for kanban generated planned order, the same applies for purch req, po ord etc. Reward points if useful

Kanban problem in Production

Hi,
I am facing the problem in Kanban procurement. We have created the production order but Kanban indicator is not active. While I have maintain the Kanban control cycle for components. And status set the blank.
Please help for resolving the problem, While Kanban indicator not active where I am wrong please helping me.
Edited by: Rajesh Tiwari on Oct 16, 2008 12:25 PM

can u tell me where to maintain this kanban indicator and for what purpose
Regards
Amit

KANBAN cycle - Change of Schedule line dellivery date.

Hi,
I have some queries in KANABAN scenario
1) How to change the schedule line delivery date generated from KANBAN cycle.
2)How to avoid generation of schedule lines from KANABAN if the Scheduling agreement was not released.
regards,
Kannaiah Naidu

Hi,
1.It is not possible to change the schedule lines of the Scheduling agreement with kanban indicator. Only work arround solution is to remove the kanban indicator. Then you can change the schedule line.
2.Using user exit, during emptying of the bin check whether scheduling agreement is released on not.If not released generate error.
Regards,
Krishna A S V

KANBAN for automobile

Hi
Can anybody help me with KANBAN cycle
i have tried making it , i have succeeded till ctrl cycle and making bins green on gr internal and external both .
But some other functions like creating proposals and with MRP ....not able to understand
I have to show the full sycle external and internal.
Is anybody having clarity on this , can share with me .
Would be of great help
Thanks
Amit

Hi,
Detailed for each of the above find as below :
KANBAN PROCESSES , PROCEDURES AND PRE-REQUISITES:
1. Stock transfer from Main Stores to Production Line
Basic rules and Prerequisites:
u2022 MRP type must remain as it has been like u201CPDu201D or u201CVBu201D or any active MRP type.
u2022 Backflush indicator is must. It can be defined in the routing or in the material master itself. If Backflush indicator is set in the material master, then the material will be backflushed through out the plant (Material issue not required against production order). However if you want the material to be backflushed only when it is used for certain products, then Backflush indicator should be set in the routing ( in the component allocation against operations).
u2022 Confirmation should be done for each operation in the production order either individually (CO11n) or collectively (CO15). Confirmation posts goods issue of components (relevant to confirmed operation/s) to production order
u2022 Maintain KN01 storage location in the field in Production Storage Location of MRP2 view in the material master. Back flushing will take place from this location. Field - Storage location for external procurement (EP) should be MN01 (Main Stores) in the material master.
u2022 KN01 - Kanban Storage Location stock is excluded from MRP.
Process steps:
1. Create supply area for Kanban storage location (KN01). TC: PK05
2. Extend the material to Kanban storage location. TC: MMSC
3. Make the necessary changes in the material master as explained above.
4. Create Kanban control cycle. TC:PKMC
5. Print the barcode. TC:PK17
6. Set the kanban status to EMPTY by scanning the barcode. TC: PKBC. A material reservation will be created for stock transfer from main stores to KN01.
7. View the demand source view. TC: PK13n
8. Once the Main stores sends the material to shop floor scan the barcode to FULL. TC: PKBC (At the background stock transfer with 311 movement will happen).
2. External procurement from Vendor to Main Stores
Basic rules and Prerequisites:
u2022 MRP type should be u2018NDu2019 in MRP1 view of material master.
u2022 Availability check should be u201CKPu201D in MRP3 view of material master.
u2022 Material received from vendor is directly posted to unrestricted stock. Inspection at vendors place or vendoru2019s process control to ensure rejection free material. Inspection set up in Material master should be inactive.
u2022 Backflush is not required and Material is issued against a Pick List for Production Order.
Process steps:
1. Create supply area for Main stores. TC: PK05
2. If required, extend the material to main storage location. TC: MMSC
3. Make the necessary changes in the material master as explained above.
4. Create scheduling agreement. Put kanban indicator (X) in the additional data of item.
5. Create Kanban control cycle. TC:PKMC
6. Print the barcode. TC:PK17
7. Set the kanban status to EMPTY by scanning the barcode. TC: PKBC. A Schedule line will be generated for the supply of material to main stores.
8. View the demand source view. TC: PK13n
9. When the material is received at Gate, perform goods receipt into blocked stock (movement type 103). TC: MIGO
10. Once the material reaches Main stores scan the barcode to FULL. TC: PKBC (At the background GR with 105 movement will happen).
3. External procurement from Vendor directly to shop
Basic rules and Prerequisites:
u2022 MRP type should be u2018NDu2019 in MRP1 view of material master.
u2022 Availability check should be u201CKPu201D in MRP3 view of material master.
u2022 Backflush indicator is must. It can be defined in the routing or in the material master itself. If Backflush indicator is set in the material master, then the material will be backflushed through out the plant (Material issue not required against production order). However if you want the material to be backflushed only when it is used for certain products, then Backflush indicator should be set in the routing ( in the component allocation against operations).
u2022 Confirmation should be done for each operation in the production order either individually (CO11n) or collectively (CO15). Confirmation posts goods issue of components (relevant to confirmed operation/s) to production order
u2022 Maintain KN01 storage location in the field - production storage location of MRP2 view in the material master. Back flushing will take place from this location. Field - Storage location for external procurement should be KN01 in the material master.
u2022 Material received from vendor is directly posted to unrestricted stock. Inspection at vendors place or vendoru2019s process control to ensure rejection free material. Inspection set up in Material master should be inactive.
Process steps:
1. Create supply area for kanban stores (KN01). TC: PK05
2. Extend the material to Kanban storage location. TC: MMSC
3. Make the necessary changes in the material master as explained above.
4. Create scheduling agreement. Put kanban indicator (X) in the additional data of item.
5. Create Kanban control cycle. TC:PKMC
6. Print the barcode. TC:PK17
7. Set the kanban status to EMPTY by scanning the barcode. TC: PKBC. A Schedule line will be generated for the supply of material to kanban store.
8. View the demand source view. TC: PK13n
9. When the material is received at Gate, perform goods receipt into blocked stock (movement type 103). TC: MIGO
10. Once the material reaches shop, scan the barcode to FULL. TC: PKBC (At the background GR with 105 movement will happen).
4. In house production (Between one sub-assembly line to Main assembly)
Basic rules and Prerequisites:
u2022 MRP type should be u2018NDu2019 in MRP1 view of material master.
u2022 Availability check should be u201CKPu201D in MRP3 view of material master.
u2022 Backflush indicator is must. It can be defined in the routing or in the material master itself. If Backflush indicator is set in the material master, then the material will be backflushed through out the plant (Material issue not required against production order). However if you want the material to be backflushed only when it is used for certain products, then Backflush indicator should be set in the routing ( in the component allocation against operations).
u2022 Confirmation should be done for each operation in the production order either individually (CO11n) or collectively (CO15). Confirmation posts goods issue of components (relevant to confirmed operation/s) to production order
u2022 Maintain KN01 storage location in the field - production storage location of MRP2 view in the material master.
u2022 Maintain u2018Kanban Production schedule profileu2019 in Work scheduling view of the material master.
u2022 Material should have a valid BOM & Routing.
Process steps:
1. Create supply area for Kanban store (KN01). TC: PK05
2. Extend the material to Kanban storage location. TC: MMSC
3. Make the necessary changes in the material master as explained above.
4. Create Kanban control cycle. TC:PKMC
5. Print the barcode. TC:PK17
6. Set the kanban status to EMPTY by scanning the barcode. TC: PKBC. A production order will be generated (with release status).
7. View the demand source view. TC: PK13n
8. Confirm the operations. TC:CO11n / CO15
9. After the confirmation of last operation, scan the barcode to FULL. TC: PKBC (At the background GR with 101 movement will happen).
Tcodes used in KANBAN:
Create Supply Area
(Tcode: PK05)
Create Control Cycle
(Tcode: PKMC)
Kanban Transaction through Scanning or
Manual operation.
(Tcode: PKBC)
Event Driven Kanban u2013 Requirement generation.
(Tcode: PK23)
Goods Receipt u2013 India Specific Process
(Tcode: PKBC)
Kanban Board u2013 Demand Source view
(Tcode: PK13N)
Kanban Board u2013 Supply Source view
(Tcode: PK12N)
Kanban Evaluation
(Tcode: PK18)
Kanban Correction
(Tcode: PK50)
Kanban Locking & Deleting
(Tcode: PKMC)
Hope will work for you.
Regards,
R.Brahmankar

How to use the text type in SAP Routine

Hi,
The following fields has to be populated in Stock transport order text fields at the time of saving the document & to be copied into delivery document
1) Material type
2) Receiving storage location
3) Production supply Area
STO
Delivery
EWM Delivery
Origin of the field value
Material type
New text type to be created
(90)
New text type to be created (Z003)
New text type to be created
(Z003)
Available in EKPO table (field name is MTART)
Receiving storage location
New text type to be created
(91)
New text type to be created (Z004)
New text type to be created
(Z004)
Available in EKPO table (field name is LGORT)
Production supply Area
New text type to be created
(93)
New text type to be created
(Z006)
New text type to be created
(Z006)
To be retrieved from Control cycle table (PKHD-PRVBE), if the Kanban indicator (EKPO-KANBA) is ‘X’.
With Best Regards,
SDN user.

Hi,
You canr use text modules in script. You have to use standard texts .
Standard text are maintained in SO10 transaction.
you can create translation text for other languages also . So based on logon language it will print translation text.
go to SO10
give textname it say Ztextname id as ST and language as EN
say create, then you will get editor there maintain your text and save it . then come back . Now change language (say for german DE) say create and eneter translation text and save it.
so now you have created a text called ztextname which you can use in your script.
Inorder to insert the texts in your script do as below
go to any window editor and select path
Insert->texts->symbols->standard symbols
then you will get popup in which you have to mention all the parameters that you have created earlier.
after inserting just change language EN to sy-langu
Reward points if useful
About text elements Sravan already given some informatiomn
Regards,
Nageswar

Suggest a TABLE CONTAINING THESE FIELDS

E1MBXYJ : Create Goods Movement from Non-SAP System: Item++
Segment definition E2MBXYJ001 Released since Release 620 , Segment length: 0476
<b>For the following fields. Tell me a table which contains a majority or all of the below fields</b>.
PARGB : Trading partner's business area
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
PARBU : Clearing company code
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0067. external length : 000004
CLASS : Class number
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0071. external length : 000018
UMCLA : Class number
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0089. external length : 000018
XCLAS : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 005, Offset : 0107. external length : 000001
UMXCL : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 006, Offset : 0108. external length : 000001
XNIBU : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 007, Offset : 0109. external length : 000001
BDTER : Requirement Date for the Component
internal data type : DATS
Internal length : 000008 characters
Position in segment : 008, Offset : 0110. external length : 000008
TBBEL : Article doc. no. of transfer requirement to be cancelled
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 009, Offset : 0118. external length : 000010
TBBPO : Article doc. item of transf.reqmnt item to be cancelled
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 010, Offset : 0128. external length : 000004
TBBJR : Article doc. year of transfer requirement to be cancelled
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 011, Offset : 0132. external length : 000004
OBJNR : Object number
internal data type : CHAR
Internal length : 000022 characters
Position in segment : 012, Offset : 0136. external length : 000022
AUTYP : Order category
internal data type : NUMC
Internal length : 000002 characters
Position in segment : 013, Offset : 0158. external length : 000002
QPLOA : Inspection Lot on Which the Usage Decision is Based
internal data type : NUMC
Internal length : 000012 characters
Position in segment : 014, Offset : 0160. external length : 000012
TBPKZ : Indicator: No Transfer Requirement Created
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 015, Offset : 0172. external length : 000001
TAFKZ : Indicator: do not cal up automatic TO creation
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 016, Offset : 0173. external length : 000001
KZEAR_OLD : Final Issue for This Reservation
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0174. external length : 000001
RSART : Record type
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 018, Offset : 0175. external length : 000001
PPRCTR : Partner Profit Center
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0176. external length : 000010
XMEVO : Propose quantities
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0186. external length : 000001
UMLGT : Storage Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 021, Offset : 0187. external length : 000003
UMLGP : Storage Bin
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 022, Offset : 0190. external length : 000010
MENGE : Quantity
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 023, Offset : 0200. external length : 000015
MEINS : Base Unit of Measure
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 024, Offset : 0215. external length : 000003
FKBER : Functional Area
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 025, Offset : 0218. external length : 000004
MHDAT : SLED/Best-Before Date or Date of Production
internal data type : DATS
Internal length : 000008 characters
Position in segment : 026, Offset : 0222. external length : 000008
BSSKZ : Special movement indicator for warehouse management
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 027, Offset : 0230. external length : 000001
EXIDV : External Handling Unit Identification
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0231. external length : 000020
BERKZ : Material Staging Indicator for Production Supply
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0251. external length : 000001
PRVBE : Supply Area
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 030, Offset : 0252. external length : 000010
KZECH : Determination of batch entry in the production/process order
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0262. external length : 000001
UPTYP : Subitem Category, Purchasing Document
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 032, Offset : 0263. external length : 000001
REFIX : Field defined as in SY-TABIX
internal data type : INT4
Internal length : 000010 characters
Position in segment : 033, Offset : 0264. external length : 000011
VLIEF_AVIS : Delivery
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 034, Offset : 0275. external length : 000010
VBELP_AVIS : Delivery Item
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 035, Offset : 0285. external length : 000006
XWAIT : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 036, Offset : 0291. external length : 000001
XNOEQ : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 037, Offset : 0292. external length : 000001
ILINR : IDoc line item number
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 038, Offset : 0293. external length : 000006
VOLUM : Volume
internal data type : QUAN
Internal length : 000015 characters
000003 decimal places, without sign
Position in segment : 039, Offset : 0299. external length : 000017
VOLEH : Volume unit
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 040, Offset : 0316. external length : 000003
ANZL1 : Number of Storage Units to be Placed Into Storage
internal data type : DEC
Internal length : 000003 characters
No decimal places, without sign
Position in segment : 041, Offset : 0319. external length : 000004
ANZL2 : Number of Storage Units to be Placed Into Storage
internal data type : DEC
Internal length : 000003 characters
No decimal places, without sign
Position in segment : 042, Offset : 0323. external length : 000004
LMEN1 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 043, Offset : 0327. external length : 000015
LMEN2 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 044, Offset : 0342. external length : 000015
LETY1 : Storage Unit Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 045, Offset : 0357. external length : 000003
LETY2 : Storage Unit Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 046, Offset : 0360. external length : 000003
KZKUB : Indicator: Do not create posting change notice
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 047, Offset : 0363. external length : 000001
UBTYP : Storage Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 048, Offset : 0364. external length : 000003
UBLGP : Storage Bin
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 049, Offset : 0367. external length : 000010
MBLNR : Number of Article Document
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 050, Offset : 0377. external length : 000010
MBLPO : Item in Article Document
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 051, Offset : 0387. external length : 000004
MJAHR : Article Document Year
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 052, Offset : 0391. external length : 000004
URZEI : Original line in article document
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 053, Offset : 0395. external length : 000004
GEBER : Fund
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 054, Offset : 0399. external length : 000010
FISTL : Funds Center
internal data type : CHAR
Internal length : 000016 characters
Position in segment : 055, Offset : 0409. external length : 000016
KZBWS : Valuation of Special Stock
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 056, Offset : 0425. external length : 000001
KDAUF_SD : Sales Order Number
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 057, Offset : 0426. external length : 000010
KDPOS_SD : Item Number in Sales Order
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 058, Offset : 0436. external length : 000006
XRERE : Reservation reading is mandatory
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 059, Offset : 0442. external length : 000001
XSTOR : Reverse posting indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 060, Offset : 0443. external length : 000001
BRGEW : Gross weight
internal data type : QUAN
Internal length : 000015 characters
000003 decimal places, without sign
Position in segment : 061, Offset : 0444. external length : 000017
GEWEI : Weight Unit
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 062, Offset : 0461. external length : 000003
WM_KZBEW : Movement Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 063, Offset : 0464. external length : 000001
WENUM : Goods Receipt Number
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 064, Offset : 0465. external length : 000010
GEBEH : Lot Container
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 065, Offset : 0475. external length : 000003
ANZGEB : QM - No. of Containers
internal data type : QUAN
Internal length : 000006 characters
000003 decimal places, without sign
Position in segment : 066, Offset : 0478. external length : 000009
KANBA : Kanban Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 067, Offset : 0487. external length : 000001
BSTMG : Goods receipt quantity in order unit
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 068, Offset : 0488. external length : 000015
FUNC_AREA_LONG : Functional Area
internal data type : CHAR
Internal length : 000016 characters
Position in segment : 069, Offset : 0503. external length : 000016
GRANT_NBR : Grant
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 070, Offset : 0519. external length : 000020

Hello Raja,
Related to goods receipt, the following are the main tables.
MSEG - Material document information
MKPF - Material document header
EKBE - Purchasing documnet history
Hope this helps.
Regards
Arif Mansuri

Suggest a TABLE CONTAINING THESE IDOC segment FIELDS

E1MBXYJ : Create Goods Movement from Non-SAP System: Item++
Segment definition E2MBXYJ001 Released since Release 620 , Segment length: 0476
For the following fields. Tell me a table which contains a majority or all of the below fields.
PARGB : Trading partner's business area
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
PARBU : Clearing company code
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0067. external length : 000004
CLASS : Class number
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0071. external length : 000018
UMCLA : Class number
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0089. external length : 000018
XCLAS : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 005, Offset : 0107. external length : 000001
UMXCL : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 006, Offset : 0108. external length : 000001
XNIBU : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 007, Offset : 0109. external length : 000001
BDTER : Requirement Date for the Component
internal data type : DATS
Internal length : 000008 characters
Position in segment : 008, Offset : 0110. external length : 000008
TBBEL : Article doc. no. of transfer requirement to be cancelled
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 009, Offset : 0118. external length : 000010
TBBPO : Article doc. item of transf.reqmnt item to be cancelled
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 010, Offset : 0128. external length : 000004
TBBJR : Article doc. year of transfer requirement to be cancelled
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 011, Offset : 0132. external length : 000004
OBJNR : Object number
internal data type : CHAR
Internal length : 000022 characters
Position in segment : 012, Offset : 0136. external length : 000022
AUTYP : Order category
internal data type : NUMC
Internal length : 000002 characters
Position in segment : 013, Offset : 0158. external length : 000002
QPLOA : Inspection Lot on Which the Usage Decision is Based
internal data type : NUMC
Internal length : 000012 characters
Position in segment : 014, Offset : 0160. external length : 000012
TBPKZ : Indicator: No Transfer Requirement Created
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 015, Offset : 0172. external length : 000001
TAFKZ : Indicator: do not cal up automatic TO creation
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 016, Offset : 0173. external length : 000001
KZEAR_OLD : Final Issue for This Reservation
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0174. external length : 000001
RSART : Record type
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 018, Offset : 0175. external length : 000001
PPRCTR : Partner Profit Center
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0176. external length : 000010
XMEVO : Propose quantities
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0186. external length : 000001
UMLGT : Storage Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 021, Offset : 0187. external length : 000003
UMLGP : Storage Bin
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 022, Offset : 0190. external length : 000010
MENGE : Quantity
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 023, Offset : 0200. external length : 000015
MEINS : Base Unit of Measure
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 024, Offset : 0215. external length : 000003
FKBER : Functional Area
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 025, Offset : 0218. external length : 000004
MHDAT : SLED/Best-Before Date or Date of Production
internal data type : DATS
Internal length : 000008 characters
Position in segment : 026, Offset : 0222. external length : 000008
BSSKZ : Special movement indicator for warehouse management
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 027, Offset : 0230. external length : 000001
EXIDV : External Handling Unit Identification
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0231. external length : 000020
BERKZ : Material Staging Indicator for Production Supply
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0251. external length : 000001
PRVBE : Supply Area
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 030, Offset : 0252. external length : 000010
KZECH : Determination of batch entry in the production/process order
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0262. external length : 000001
UPTYP : Subitem Category, Purchasing Document
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 032, Offset : 0263. external length : 000001
REFIX : Field defined as in SY-TABIX
internal data type : INT4
Internal length : 000010 characters
Position in segment : 033, Offset : 0264. external length : 000011
VLIEF_AVIS : Delivery
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 034, Offset : 0275. external length : 000010
VBELP_AVIS : Delivery Item
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 035, Offset : 0285. external length : 000006
XWAIT : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 036, Offset : 0291. external length : 000001
XNOEQ : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 037, Offset : 0292. external length : 000001
ILINR : IDoc line item number
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 038, Offset : 0293. external length : 000006
VOLUM : Volume
internal data type : QUAN
Internal length : 000015 characters
000003 decimal places, without sign
Position in segment : 039, Offset : 0299. external length : 000017
VOLEH : Volume unit
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 040, Offset : 0316. external length : 000003
ANZL1 : Number of Storage Units to be Placed Into Storage
internal data type : DEC
Internal length : 000003 characters
No decimal places, without sign
Position in segment : 041, Offset : 0319. external length : 000004
ANZL2 : Number of Storage Units to be Placed Into Storage
internal data type : DEC
Internal length : 000003 characters
No decimal places, without sign
Position in segment : 042, Offset : 0323. external length : 000004
LMEN1 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 043, Offset : 0327. external length : 000015
LMEN2 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 044, Offset : 0342. external length : 000015
LETY1 : Storage Unit Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 045, Offset : 0357. external length : 000003
LETY2 : Storage Unit Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 046, Offset : 0360. external length : 000003
KZKUB : Indicator: Do not create posting change notice
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 047, Offset : 0363. external length : 000001
UBTYP : Storage Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 048, Offset : 0364. external length : 000003
UBLGP : Storage Bin
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 049, Offset : 0367. external length : 000010
MBLNR : Number of Article Document
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 050, Offset : 0377. external length : 000010
MBLPO : Item in Article Document
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 051, Offset : 0387. external length : 000004
MJAHR : Article Document Year
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 052, Offset : 0391. external length : 000004
URZEI : Original line in article document
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 053, Offset : 0395. external length : 000004
GEBER : Fund
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 054, Offset : 0399. external length : 000010
FISTL : Funds Center
internal data type : CHAR
Internal length : 000016 characters
Position in segment : 055, Offset : 0409. external length : 000016
KZBWS : Valuation of Special Stock
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 056, Offset : 0425. external length : 000001
KDAUF_SD : Sales Order Number
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 057, Offset : 0426. external length : 000010
KDPOS_SD : Item Number in Sales Order
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 058, Offset : 0436. external length : 000006
XRERE : Reservation reading is mandatory
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 059, Offset : 0442. external length : 000001
XSTOR : Reverse posting indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 060, Offset : 0443. external length : 000001
BRGEW : Gross weight
internal data type : QUAN
Internal length : 000015 characters
000003 decimal places, without sign
Position in segment : 061, Offset : 0444. external length : 000017
GEWEI : Weight Unit
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 062, Offset : 0461. external length : 000003
WM_KZBEW : Movement Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 063, Offset : 0464. external length : 000001
WENUM : Goods Receipt Number
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 064, Offset : 0465. external length : 000010
GEBEH : Lot Container
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 065, Offset : 0475. external length : 000003
ANZGEB : QM - No. of Containers
internal data type : QUAN
Internal length : 000006 characters
000003 decimal places, without sign
Position in segment : 066, Offset : 0478. external length : 000009
KANBA : Kanban Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 067, Offset : 0487. external length : 000001
BSTMG : Goods receipt quantity in order unit
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 068, Offset : 0488. external length : 000015
FUNC_AREA_LONG : Functional Area
internal data type : CHAR
Internal length : 000016 characters
Position in segment : 069, Offset : 0503. external length : 000016
GRANT_NBR : Grant
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 070, Offset : 0519. external length : 000020

see the tables MSEG, MKPF.
REgards,
Ravi

Transfer Requirement not getting created

Hi All,
My query as below;
Production order is created using KANBAN (Control Cycle/Supply Area is defined) using classic KANBAN.
WM is in place and all the setting related to TR/TO creation for WM movement type 103 is in place.
When i am trying to receive this Production after completion it is not creating the TR/TO, while as material document is getting generated and shows the stock directly in interim storage type 901 without creating TR and TO.
Further i checked there is indicator in Production order i.e "Kanban indicator" that gets checked automatically when Production order is created using KANBAN Processs and if i remove that indicator forcefully, TR and TO is getting created normally.
Please provide some inputs where can be the problem and how TR and TO can be created normally eventhough KANBAN indicator is checked in Production order and where i can found the setting related to "KANBAN INDICATOR".
Appreciate your help.

Hi Maddy
Thanks very much for your response.
1. When you use KANBAN, you define separate KANBAN storage location, which is different from WM-managed replenishment storage locations, and separate KANBAN interim storage area with storage bin.
Yes different storage location is defined which is not WM-managed in supply area.
As you said Control Cycle is defined, see if the interface is properly defined for both of these Sloc.
Where i can check whether interface is properly defined or not.
2. See if you have defined the KANBAN replenishment strategy with Control type Transfer Requirements from a Storage Location which is being controlled by WM in the Customizing for Production under KANBAN > Replenishment Strategies > Define Stock Transfer Strategies
Actually for a material two strategies are defined like;
1) In-house Production strategies-0003-
supply area is defined with storage location which is IM managed.
And when this order is completed and i am trying to receive this in WM SLOC (usally whatever SLOC we have defined in supply area it proposes that SLOC at the time of receipt but i am changing this manually to WM managed SLOC) using transaction MIGO, it is directly taking the stock to 901 interim storage type and in total the stock increases but the problem is when TR is not getting created i am not able to take this to the storage bin as per strategies defined.
2) Stock Transfer Strategies-This is working fine and in that TR/TO is working fine.
3. For TO to get created automatically by the system from the transfer requirement, see if an indicator Automatic TO creation in the replenishment strategy is set or not. Yes this is set for stock transfer strategies but i didn't find option to check the TO creation automatically for in-house production strategy
4. Also, check that you have set up a suitable replenishment movement type for KANBAN in the Customizing for Warehouse Management under Activities > Transfers > Define Movement Types (i.e.standard is 350 for KANBAN replenishment)-Yes this is also defined correctly.
Appreciate your more inputs on this.

Issue components for a subcontracting scheduling agreement

Hello,
Please can anyone tell me how (steps) to issue components on subcontracted item on a scheduling agreement . Item is also set up with KANBAN indicator so GR is done thru changing KANBAN bin status.
Thanks
Mira

You can view, Explode during creeation of delivery schedule for SA. Use ME38 transaction you will see the BOM in item details

Delivery complete indicator set by partial goods receipt in kanban orders

HI Experts,
we recently upgraded to ECC 6 DIMP EP 6. Now for kanban production orders delivery complete indicator is set for partial goods receipt. Under delivery tolerance is zero. Is there any notes available for this issue. Manual production order goods receipt is fine.
THanks
RIjil

Hi,
Let me try and understand your scenario better. You have a production order triggered by KANBAN. You then do a GR via inventory management of a partial quantity. Would you then GR the remaining quantity?
The reason I ask is because this is KANBAN production, the bin being filled multiple times for the same trigger does not sound right. The system behavior of not expecting further deliveries (by setting delivery complete) seems appropriate.

External Kanban (full to empty) - Scheduling Agreement Schedule Lines

Hello Sir/Madam,
Our control cycle is using external replenishment procedure with "0002" (i.e. working with Scheduling Agreements ).
Indicator u201CSeparate GR posting when changing status to fullu201D is not set.
Symptom:
When the Kanban container is empty, I perform a PKBC to sign the status from "Full to Empty" and I save it. The system generates a delivery schedule and an email is sent to the vendor. This can be proved by MD04.
The problem is that the system generates another delivery schedule after few minutes and also another email is sent to the vendor. So, the delivery schedule and the email are incorrectly done twice.
I am wondering how the system setup is able to generate automatically a new delivery schedule which is not correct.
Please could you suggest me some solution.
Regards
Luca

I think in this case, that if no user exits were activated in your system, you should create an OSS message for SAP.

Kanban issue - Setting for new Kanban functionality in ECC 6.0

Hi, I am facing a problem while recieving stock from a production order. The system does not create a transfer requirement or a TO.
Let me give you a brief background.
This is a new functionality introduced in ECC 6.0 for working with kanban in WM.
Supply area is created for WM location.
Control cycle is created for material, supply area. Warehouse, storage type and Bin is maintained in control cycle record. When the GR is done for production order material is recieved in this bin.
1) Now when the Kanban is set empty a production order is automatically created.
2) Once the production order is confirmed the material automatically shows up in the bin.
A material document is created which shows IM movement type 101 and WM movement type 103. Also in material document Immediate auto TO checkmark is blank.
3) PROBLEM - System does not create a TR or a TO. the material automatically shows up in the Bin. How can we enable an auto TR and TO creation.
Following are the settings which I have already checked:
1) In IMG, WM movement type 103 has auto TO indicator set.
2) IM-WM interface for 102 movement type and 103 movement type is maintained.
The main problem is: Although the material document displays WM movement type 103 and the stock lies in WM bin, System never created a Transfer requirement or a Transfer order.
I would really appreciate if anyone can help me in this.
Thanks

Hello,
I am not sure about your settings, please refer below sap link
[Kanban Replenishment |http://help.sap.com/saphelp_47x200/helpdata/en/95/e81fa4f57011d194aa0000e83dcfd4/content.htm]
Regards
Pradeep Kumar

KANBAN Indicator

Similar Messages

Maybe you are looking for