Experience in implementing the roll out project in SAP (2)

ZZ http://blog.sina.com.cn/s/blog_3eeba4010100c5vr.html ~ Type = v5_one & label = rela_nextarticle)

 

In the previous article, we talked about the implementation idea of the roll out project and the precautions for project management. This article focuses on technical and data issues.

In terms of technology, due to the many limitations mentioned in the previous article, it is also different from the new project. I only have some knowledge about logistics, so I can only briefly discuss the considerations for logistics configuration. In general, it is important to note that when configuring the system, do not ignore what already exists. Some configurations may have been done in the original project, but they are not the standard settings used. Pay special attention to these configurations when creating the roll out project, do not confuse the parent company's business because of roll out.

Technical issues cannot be discussed in different categories. It is a bit messy.

1. language problems.

Especially in cross-country roll out projects, you must pay attention to language issues. For example, if a language is selected in the country settings, the countryCodeIt is displayed in the Chinese language. If this is not possible in the actual business, do not select this language in the country code, so that the system can automatically determine based on the login language.

Another example is that the form of the purchase order has multiple languages. If you want to copy the changes, you must copy them in multiple languages. Copying in only one language may cause a problem with the purchase order in other languages.

2. Data Classification

Focus on material types. Many roll out projects involve inter-company transactions. Whether it is cross-company sales or inter-company procurement, if such inter-company transactions adopt a system standard model, it will involve the application of the same material code between multiple factories. At this time, what kind of material is a very important question.

There is a restriction on the type of the item. For example, Roh generally only allows external procurement and does not allow self-made materials. In inter-company transactions, raw materials are often used in this factory, and finished products should be used in another factory. At this time, if it is set to the raw material type, production will not be available in another factory.

There is also view control in the material type. There is no work plan view in Hawa. If a factory purchases materials from another factory and then sells them directly, it is usually set to the Hawa type. But in another factory, it is a self-made product and needs to be produced.

Such problems often lead to material type classification problems, which need special attention.

3. Procurement approval strategy

If the approval policy is not used in the original project and the subsidiary needs to use it during roll-out, note that the feature settings should be distinguished by company code or procurement organization, you cannot simply use a document type to implement this function.

4. Special material acquisition type

In the mrp2 view, a field is called special procurement type. Here we can define that materials are produced in another factory. Such fields related to inter-company transactions should be validated.

5. Output condition records

Remember to use Mn * to maintain various output condition records. Note the maintenance of export tax conditions, especially for multinational corporations.

6. Pay attention to the correct maintenance of the country in the basic data settings

For example, the country settings of shipping piont are sometimes copied directly from an original project. When you change the settings, you only need to pay attention to the address details. The country is different. This is easy to ignore. Because the concept of country is too big, it is generally ignored. Pay special attention to roll out of multinational corporations.

7. EDI Configuration

In the roll out project, inter-company transactions are sometimes used. The automatic receipt of invoices for inter-company transactions can be achieved through EDI, so pay attention to the relevant configuration of EDI.

8. Tax Code settings

SAP has a special notes for this. How is the tax code determined on the F2 invoice during cross-company sales? It can be determined by the shipping factory and the customer's home country, or by the sales organization and the customer's home country. The default value is the previous one. If you want to use the latter one, you need to manually add the notes.

9. Use of ERS

In the original project, only external vendors are generally available and the ERS function is not enabled. However, in the roll out project, ERs may be used, because internal suppliers are generally trustworthy.

10. gr-based IV

The invoice verification based on receipt is generally enabled in the original project. However, po-based invoice verification may be used in inter-company transactions. Po-based invoice verification is preferred, especially when the cross-company procurement process is used to send invoices using EDI at the same time. In this way, the recipient can be recorded immediately after the shipping is billing. If the receipt-based invoice verification is enabled, because the receipt is not completed, IDOC cannot be transferred.

11. MRP running Scope

Multiple factories run MRP together, which may be frequently encountered in roll out projects. Make sure to modify the configuration.

12. Client-level field selection

For example, material master data, supplier master data, and inforecord all have client-level or transaction code-level field selection settings. Be careful when modifying this type of settings. I have changed the settings of a material master data. In order to set a field for a factory, I changed all the field groups of the original project to the factory level and restored them to the original settings, modify the attribute of this field in the required factory. In the end, we found that this was not a week-long consideration, which affected other online companies and caused a bad impact.

There are many technical aspects and data aspects that need attention. This article only lists a small part of what I have learned.