Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
R3483 does not create WO messages

this is the process that i follow.
1.- Crearte a forecast (p3460) type BF.
2.- Run R3483.
3.- Check P3411. Only creates PO messages but Manufacting ítems doesnot creates a WO messages but only shows a messages taht says "leadtime is zero".
4.- Run R30822aLeadtimes roll up but it doesnot populate manufacturing leadtime.
i had check P41026- add info system but i dont know what to do beucause i follow the process to do it well.
Answers
-
The information you provided is pretty limited, and let me try to guess:
1. You should run R3482 instead of R3483, however this should not relate to your issue.
2. R30822A leadtime rollup affected by lots of setups and not easy to explain clear here. Go for Doc. ID 1381378.1 to make sure all setups are correct.
3. Go to P41026 of your Mfg item and row exit to Additional System Info. By giving the field Fixed/Variable = F and any number to field Leadtime Level, and rerun you R3483 to see f you can get your WO message from P3411.
4. Extra point why R3483 ? Do you have the same issue if run by R3482 ?
Regards,
John
-
THANKS I ADD MANUALLY LEADTIMES AND AFTER RUN r3483 AGAIN AND SHOWED WO MESSAGES.
SO I NEED TO CHECK LEADTIMES BECAUSE I USE FIXED LEADTIME, BUT WHEN I RUN 30822A IT DOESNOT POPULATE LEADTIME MANUFACTURING. AFTER THIS I POPULATE MANUALLY MANUFACTURING LEADTIME (MQL) WITH "1" AND RUN THE REPORT AGAIN.
SO POPULATED THE FIELDS BUT I AM NOT SURE IF IT IS CORRECT TO DO IT? -
1. Suggest make sure you know the difference between F and V. F and V do not relate to R30822A calculation logic but when WO created by giving requested date, how system is based on to provide the start date. F - system is based on Leadtime Level to backward the WO start date, that is no matter how big the quantity on WO you will get the same start date. V- system is based on Leadtime per Unit multiplied by WO quantity to backward the start date.
2. No matter F or V chosen, when try to calculate the Leadtime Manufacturing, the MLQ has to be > 0. However it does not mean to put 1 there is correct. The number on MLQ represents the Leadtime Level calculated by system is based on this number. For example some item can be produced very quick so I may put 1,000 to MLQ so if the Leadtime Level goes 2 means every 1,000 EA need 2 days to manufactured. Notice the TIMB (Time Basis Code) setting on routing affects the result also.
Go to Support Doc ID 1381378.1 to get completed explanation on Leadtime calculation