In case if you want to assign a particular purchasing requisition to a vendor other than the regular vendor, you can use the “manual assignment” functionality in ME57.

You have to enable this functionality by plant in the config. Below is the process.

 Config settings

Select Plant for the Regular Vendor Setting

Before Selecting Regular Vendor A List Will be displayed with all the possible options. User will have to select by double clicking on the desired vendor

 Selecting Regular Vendor In Info Record

After Selecting One InfoRecord as “Regular Vendor”, user no longer gets the list, although they have multiple inforecords. Purchase Requisitions are automatically allocated when “Assign Automatically” is selected.

(A post i promised to put up long long ago, finally is here. You can find original post on Grid Conversions here)

-> Select the path below

SPRO -> Logistic General -> AFS Material Grids -> Conversion

Here you have to do two things.

-> Define the conversion type. If you want to say maintain conversions based on the different languages, you will have to maintain one conversion type per language.

-> Define which conversion type is called in which scenario. You can basically use  the conversion based on the material, Customer/Vendor and user or any of those combinations.

Now you have to find the characteristic(s) you have used in your grid.

-> GoTo CT04

-> Click on the conversion button

-> Click New Entries Button and Maintainthe line and the grid entry against your base value. Line enrty is how the value is displayed when the value is displayed in a line entry. Grid entry determines how the converted value is displayed in the grid display.

-> Now you may use your conversations in the depending documents like PO, SO and materials. Just select the Doc. Conv. Type button to change the conversion type to which you prefer.

Note, the base value is set at “S”, but the size shows as “X”. This is the line entry value we assigned in the characteristic for this conversion type.

If you click the grid entry and go in it will show “Z” as the size mapped for base size “S”. This is because we maintained the grid entry size as “Z” in characteristic. Do not get confused. This is a 3D Grid. I have only converted one of these characteristics.

Now you can maintain the values in converted grid value. In the case of below, you maintain the “X RED1” and “X GRE1”  instead of “S RED1” and “S GRE1”.

How to maintain grid conversion defaults in vendor master

Go to XK02 -> Environment -> AFS Additional Data

Maintain the default value under vendor ID

How to maintain the grid conversion in customer master

Maintain AFS Additional Data

SPECIAL NOTE:

In the newer releases of AFS the conversion at material level is not made active(this field is grayed out). I found the note 1322001 in this regard, which explains the steps to get the functionality back only in AFS environment if you need it. Please refer SAP NOTE 1322001 for more details.

If you find this post helpful, please let me know by Liking this post.

Yes, one of the MRP issues, I found few times in my consulting carrier happens due to the exhaustion of numbers allocated. For an example, if you run out of numbers in allocated planed order number series, MRP will not be able to create a planned order. Same logic applies for the Purchase requisitions too. Check this and if the numbers are exhausted or nearing the upper limit of the allocated number series, you have to extend your number series or allocate a new number series for the document type in question.You can check these settings using transaction OMI2. I hope you found this piece of advice interesting. If you like to contribute to the AFS knowledge pool, please write to me at azwath@yahoo.com

If you find this tip helpful, please click the “Like” button below.

We upgraded one of our instances from AFS version 3.0b to 6.0 some time back. We had few issues with migrating categories. But after migrating, we never had a need to create a new category in 6.0 environment. But when we had to we faced few issues.

To configure a category you have to first create a “Characteristic”. Then in SPRO, you have to create a category structure and then create a coverage strategy and assign the coverage strategy to the category structure. Configuration node can be found following the path SPRO -> Logistics – General – >AFS Categories.

We followed the process but the results did not work as we intended. With the help of AFS support team, we found Relevance and Conversion buttons were missing on the CT04 screen and as a result configuration could not be completed properly. So they recommended the SAP NOTE 1041015 and it solved the issue for us. It put the buttons on the CT04 screen and enabled us to complete the configuration.

Caution: Please read through SAP documentation before implementing notes. If required seek the SAP support. These steps might not work, or even might do harm in your case.

Today Buddhists all over the world are celebrating the 2600^th Sambudhdhathwa Jayanthi. Sri Lankan people join the celebrations in a grand way. It was great to see all these. Just an image to celebrate the day from Baudhdhloka Mawatha, Colombo, Sri Lanka.

SAP, traditionally based on client based UI (or fat clients) did show some move towards the thin web based technology. In fact some of them were very interesting developments. But still I believe SAP has some catching up to do.

One difference I see between SAP and companies like Google, is that, SAP tries to do more or less the same thing they do with their fat clients, on the web with their thin clients too. This for me has two problems. First it will require larger band widths (meaning slower to the users); second it doesn’t use the power of online technology brings. For an example, while Spread sheet solutions on Google Docs have traditional functions which MS Excel used to has, they also have very interesting functions to get the real-time financial report using the power of online technology. Forms in Google docs is another great example for using the power of being online.

Again, a system like SAP requires the reliability and security levels which may be compromised in the online world. So it is correct to say, SAP is best used with the fat client technology today. But very soon, I am sure; SAP will come up with a real web solution making users to work online, just like any other online application.

BTW, if you are wondering what chrome book is, it is a kind of a notebook computer, which doesn’t contain any installed applications. But it is always connected to the web, making available to the user web based programs like Google Docs, Gmail and other tons of stuff. Chrome Books will not install software in their hard drives. So there is no need to upgrade and maintain anything. It is secured from the source, so even a virus guard is not required. Obviously this makes the system faster, and smarter. Cost for maintaining the system is much less compared to a traditional network. All the files will be saved in the “Cloud” not in your hard drive. So what you do is independent of the device you use. You might lose the device, not the work. And when it comes to the price, it is based on subscription just like using a mobile phone. Interesting isn’t it?

For more information follow the link below

http://www.youtube.com/user/GoogleDevelopers

• Configuring AFS SD for SAP AFS Best Practices.
• Configuring Standard Sales Order, Pre-order, Rush order, Purchase to Order (PTO), make to order (MTO) 3^rd Party order, Debit, Credit, Cross Company, Returns and Samples Order Types.
• Customer Master and Forwarding agent set up.
• Part of the SD team, with capable of collecting requirements and converting into functional specifications.
• Should have cross module (MM and FI/CO) integration experience to build and test the end to end process.
• Must to have prior EDI processes experience.
• Capable of building and reviewing  business and technical documentation to ensure test plans meet technical and business requirements.
  • Support system changes and training in the areas of AFS Grids, Seasons,  Allocation & Deliveries, Rescheduling and ATP.  Make changes in configuration settings, program variants and Allocation Mass sets.  Advise on ABAP program changes in the above areas (user exits, reports, performance enhancements). Review and/or log OSS notes.
  • Document functional requirements, develop functional specs for program changes, make configuration settings, perform testing, conduct system demos and work with users providing training and testing support.
  • Ensure solution integration and integrity within the process areas
  • Ensure that the technology solution delivered meets the requirement of the functional business leaders
  • Motivate and inspire a talented team of IT specialists using a collaborative approach to create, plan and promote diversity, including the ability to work effectively across the organization
  • Provide support to customer service organizations by supporting project requirements

Essential Functions:

• Hands on experience within the SAP AFS SD module, with specific experience in the Allocation, Outbound Deliveries, Rescheduling and Available to Promise areas
• Minimum of two full life cycle implementations in an AFS environment.
• Proven experience with requirements gathering and process design.
• Ability to work closely and effectively with end users.  Strong ‘people’ skills are essential to ensure customer satisfaction
• A good understanding of consumer products business model or global models in a consumer products organization
• A good understanding of various SAP system landscapes
• Ability to work with multiple priorities in delivery and project organizations
• A collaborative approach including effective conflict management
• Excellent communication skills both verbal and written
• Influencing, negotiating and relationship management skills
• Ability to travel 25% of the time (domestic and international)
• The ability to lead change and to provide direction within a constantly changing and dynamic business

Please contact Chase with below LinkedIn Link

http://www.linkedin.com/in/chasevanhuisen

AFS has a design edging towards MTO rather than MTS or Made To Stock. This mentality of AFS can be seen in the inability to use various MRP types. Even the simple minimum stock level ordering is not possible through the MRP type relevant for the AFS materials in the stable versions of AFS. This suggests, AFS is more like to be deployed with the MTO mindset than a MTS mind set.

Use of MTO with AFS presents a set of unique challenges. All the demands and supplies are allocated to a customer orders like Sales Order (SO) or a Sales contract. This multiplies the amount of transaction data. For an example if you are going to produce 10,000 pieces in a MTS scenario, you may use one production order for the quantity of 10,000, while in the case of MTO, if there are 10 small customer Pos making the demand of 10,000 with 1000 pieces each, you will have 10 production orders instead. This will increase the number of data available in the system. But on the positive side you will gain more and more control over the order. You are much leaner in manufacturing, as you always try to only manufacture in the quantities customers need.

Data multiplies further with the use of sizes too. If each of the 10 SO had 5 grid values each, the number of table entries in the relevant at the detail levels will increase by 5 times. This again accounts for the increase of data in the system. Increase in the data will slow down the system, if frequent archiving is not done.

Although AFS in my opinion is more inclined towards MTO, I believe there are some areas needs to be modified to better cater MTO business. One of these areas is the subcontracting of goods. Subcontracting is a very common in specially the apparel industry. But unfortunately AFS solutions are not geared to the replicate the physical scenarios in the system in MTO. But when it comes to MTS, they have excellent features. But the good news is there are well established work around available to manage MTO subcontracting in AFS.

There are few other limitations when it comes to MTO as well. One of these is the use of Scales to maintain different discounts for different quantities. Although behavior of scales do vary depending on the configuration, in a pure MTO scenario, you can maintain Scales in purchasing not for the entire PO but only for the particular LI of the PO. If you are using AFS, you may have more insight to these problems. Please leave your thoughts as a comment to this post.

Please note, these are just my thoughts depending on what I have seen over the years. There may be differences in your experience. You can always leave your comments below.