Convert Smartform to PDF 转化smartform到PDF格式
如果仅仅是自己想临时dowload某个smartform打印结果 |
SAP汽车行业package配置常用TCODE(VMS部分)
SAP Automotive customizing Tcodes (Vehicle Management System (IS-A-VMS))
Customizing for VMS
Transaction Code | Description |
Number Ranges | |
| OVELO2 | Define number ranges for internal vehicle number |
| OVELO3 | Define number ranges for action control determination |
| OVELO8 | Define number ranges for determination of configuration change profile |
Other | |
| OVELO19 | Define VMS roles |
OVELO7 | Assign own dialog messages |
Vehicle Search Area | |
| OVELO27 | Define sharing levels |
| OVELO18 | Define vehicle search areas |
OVELOVSRINIT | Initialize category maintenance |
| OVELO20 | Define vehicle categories |
| OVELO21 | Assign roles and vehicle categories |
Control | |
| OVELO1 | Define actions |
OVELO12 | Define vehicle status |
OVELO5 | Define external status |
OVELO13 | Determine availability |
OVELOL | Define vehicle locations |
OVELO14 | Define vehicle usage |
| OVELO11 | Define action controls and actions matrices |
Message Determination | |
OVELOM04 | Define field catalog for messages |
OVELOM01 | Maintain condition tables |
OVELOM11 | Define access sequences |
OVELOM21 | Define message types |
OVELOM31 | Define message determination schemas |
OVELOM41 | Assign message determination schema to plant |
Enhancements | |
OVELO6 | Enter technical data for actions |
| OVELO4 | Define additional data for vehicle |
Master Data
Transaction Code | Description |
Material Master Record | |
| MM01, MM02 | Create and change material master records for vehicle models |
Classification System, Variant Configuration | |
| CT04 | Create and change vehicle characteristics with characteristic values |
| CL04 | Create, change classes |
| CU50 and CL30N | Group characteristics on interface |
| CU41, CU42 | Create, change configuration profiles |
| CU01, CU02 | Create, change relationship and object dependencies |
Pricing | |
| VK11, VK12 | Create and change variant conditions in SD |
| MEK1, MEK2 | Create and change variant conditions in MM |
IPC (Internet Pricing and Configuration) | |
| CU31, CU32 | Create, change knowledge-base object |
| CU34, CU35 | Create, change run-time version |
Business Partner | |
| XK01, XK02 | Create, change vendor (creditor) centrally |
| XD01, XD02 | Create, change customer (debtor) centrally |
VMS Roles | |
| VELORM | Assign vehicle models to VMS role |
| VELORO | Assign organizational data to VMS role |
| VELORU | Assign VMS roles to user |
Vehicle Management System
Transaction Code | Description |
| VELO | Vehicle Manager |
| VELOM | Status monitor for the vehicle IDoc |
Basic Data | |
| VELOS | Define action control determination |
| VELOC | Define sales campaigns |
| VELOP | Define configuration change profiles |
| VELOPR | Analyze configuration change profiles |
| VELOOBJC | Add object characteristics to a configuration |
VELOK | Define message condition records |
| VELOBWC | Assign class characteristics to BW characteristics |
Reports for Administrators | |
| VELOV | Define variants for actions in batch |
| VELOB | Perform actions in a batch |
| VELOR | Update reservation queue |
| VELOE | Correct incorrect vehicle statuses |
| VELOP01 | Log: status monitor for vehicle IDoc (not in menu) |
| VELOP02 | Log: update reservation queue (not in menu) |
| VELOP03 | Log: action execution in Vehicle Manager (not in menu) |
SLG2 | Application log: delete old logs (not in menu) |
smartform的trace
有些时候smartform的form画得不对，在设计form layout的时候check是不出错的，但是一旦跑了function, exception就返回了。但是单单凭这个很难知道到底哪错了。
那么有一个有用的TCODE SMARTFORM_TRACE
switch on以后就会捕捉到smartform中报的具体的错误
ATP与RLT
1，ATP(Avaliable To Promise)
ATP实际上代表一个产品的预计可用数量，就是说，在未来的某一个时刻某一个产成品可以提供给客户的数量，
2，RLT
RLT（Replenishment Lead Time）的概念，叫补货提前期
RLT会影响ATP的结果。
RLT有对于in-house production和external procurement两种产品的定义不同：
对于In-house production又有两种不同的计算方法
ATP实际上代表一个产品的预计可用数量，就是说，在未来的某一个时刻某一个产成品可以提供给客户的数量，
2，RLT
RLT（Replenishment Lead Time）的概念，叫补货提前期
RLT会影响ATP的结果。
RLT有对于in-house production和external procurement两种产品的定义不同：
对于In-house production又有两种不同的计算方法
The following options exist for materials produced in-house if the replenishment lead time is included in the availability check:
The Total replenishment lead time field is maintained.（物料主数据MRP3 视图）
In this case, the time maintained in this field is used for the availability check.
The Total replenishment lead time field is not maintained.In this case, the system reads the in-house production time and, if available, the goods receipt processing time, and interprets the total of these two times as the replenishment lead time for the availability check.
in-house prodn. time+GR processing time in MRP2 view
以下图说明了RLT对ATP的影响
n You can take into account all inward and outward movements. It is recommended, however, that you only implement an availability check at the end of the replenishment lead time.
n The replenishment lead time can be specified for each material.For example, trading goods: planned delivery time + processing time for goods receipt,
Finished goods: in-house production time
n The system assumes that the material will be available at the end of the replenishment lead time by the latest.
n The availability check is only run until the end of the replenishment lead time.
n If you check availability in case 4 without including replenishment lead time, the result is the same as for case 2. The customer requires a complete delivery. You cannot make 20 units available until the same date on which the last purchase order for 60 units arrives (inward movement).
n However, if the system checks availability using the replenishment lead time, you can make 20 units available for the date on which the purchase order with 50 units arrives (inward movement). Only the inward and outward movements that take place within the replenishment lead time are included in this check.
关于ATP与RTL的配置
https://www.sdn.sap.com/irj/sdn/thread?messageID=4309121
http://sapfunctional.com/SD/AvailabilityCheckConfiguration.htm
partial delivery control
关于允许做partial delivery的控制在customer-material info record里。
TCODE VD51
TCODE VD51
n The indicator for controlling complete/partial deliveries is proposed from the customer master record. The proposal for the item level comes from the customer-material info, if a customer and material agreement has been maintained there. These indicators can be manually changed during sales order entry.
n The customer may require, for example, a complete delivery which means that all the items in the sales order should be delivered together. If the customer agrees to a partial delivery, the order can be met in several deliveries.
n If you choose "Complete delivery", you can determine that all the items in a whole order must be delivered together. At item level, you can also decide whether you can split the delivery quantities.
n The following partial delivery agreements exist:
Ÿ _ Partial delivery permitted
Ÿ A Enter a delivery with quantity not equal to 0
Ÿ B Only create a delivery (also with quantity = 0)
Ÿ C Only complete delivery can be carried out
Ÿ D Preferred subsequent delivery
route的决定过程
The route is the transport channel of an outbound delivery from the delivering plant to the ship-to party.
n It can consist of more than one section and has a beginning point and an end point.
n You can use this route to define the actual transit time (period in which the goods are being transported) and the lead time for transportation planning.
n The route is normally determined for each document item in the sales document.
The automatic default value can be changed manually at a later date, if you wish to have alternative routes.
n The system tries to determine a route for every item to be delivered.
n The SAP system uses four separate points as search keys for determining the route automatically Normally this data is defined in master records and in Customizing:
- � the departure zone in Customizing for the shipping point
- � the shipping condition in the sales and distribution-specific data for the sold-to party (View: Shipping)
- � the transportation group in the sales and distribution-specific data for the material (View: SD: General/Plant)
- � the transportation zone in the ship-to party general data
