Forum Replies Created
You can also try LTMC transaction (Data Migration Cockpit).November 2, 2023 at 4:47 am in reply to: Impacts of Factory calendar reassignment to plant in OX10 on MM/PP/SD activities #48519
In SAP, a factory calendar plays a crucial role in scheduling and planning activities in the Materials Management (MM), Production Planning (PP), and Sales and Distribution (SD) modules. When you reassign a different factory calendar to a plant using transaction OX10, it can have significant implications on various activities in these modules:
Materials Management (MM):
Procurement and Purchasing: The factory calendar defines working days and holidays for the plant. When you change the factory calendar, it affects lead times for procurement and purchasing processes. For example, if you change the calendar to include more working days, the lead time for receiving materials may be reduced, impacting reorder points and safety stock levels.
Changes to the factory calendar can affect inventory management. If you add more working days, you may need to adjust reorder points, reorder quantities, and safety stock levels to match the new calendar.
Material Requirement Planning (MRP):
MRP calculations take into account the factory calendar to determine when materials are needed. Changing the factory calendar can impact the MRP run results, potentially leading to different order recommendations and schedules.
Production Planning (PP):
Work Scheduling: Factory calendars are used to schedule production orders, work centers, and capacity requirements. Changing the factory calendar can affect the production schedule and capacity planning. For example, if you add more working days, production lead times may be reduced, allowing for more efficient production planning.
Capacity Requirements Planning (CRP):
Capacity planning relies on the factory calendar to determine available working time. A change in the factory calendar can impact capacity requirements and scheduling in the CRP process.
Shop Floor Execution: Changes to the factory calendar can affect shop floor activities and the production workforce. Scheduling changes may require adjustments to labor and resource planning.
Sales and Distribution (SD):
Delivery Schedules: The factory calendar can impact delivery schedules and lead times for customers. If you change the calendar to include more working days, customers may receive their orders faster.
Order Promising: Factory calendars are used in order promising to provide realistic delivery dates to customers. Changing the calendar can affect the availability and commitment of products to customers.
Shipping and Transportation:
Altered factory calendars can affect shipping and transportation schedules. You may need to adjust transportation planning, carriers, and delivery windows to accommodate the new working days.
You cannot use the F.13 transaction in SAP to automatically clear downpayments. The F.13 transaction is primarily used for clearing open items in the accounts receivable and accounts payable subledgers, and it doesn’t have specific functionality for clearing downpayments.
To clear downpayments in SAP, you typically use the transaction code F-39 (Post Incoming Payments) for accounts receivable downpayments and F-37 (Clear Customer Down Payment) for customer-specific down payments. For vendor down payments, you use F-48 (Post Vendor Down Payment) and F-54 (Clear Vendor Down Payment).
To print rotated barcode labels on a Zebra printer with a 3-label roll using SAP Smart Forms, you can achieve the desired result by either using text positions or windows, ensuring that each label’s content is properly rotated and positioned within the constraints of your label paper.
In SAP, finding a service master from a Purchase Order (PO) when it’s not linked to an Outline Agreement (OA) can be a bit more challenging. Try these steps:
1. Transaction Code ME23N: Start by accessing the PO you want to find the service master for using transaction code ME23N. Enter the PO number and press Enter. This will display the PO details.
2. Item Details: Within the PO details, navigate to the item for which you want to find the service master. You can do this by clicking on the “Item Overview” tab or a similar option depending on your SAP configuration.
3. Service Tab: Once you are on the item details screen, check for a “Service” tab or a similar section. This tab should display information related to the service item on the PO.
4. Service Number: In the “Service” tab, you should see a field labeled “Service Number” or something similar. This is where you can find the service number associated with the service item on the PO.
Thanks for the feedback! You need access to an SAP system to be able to practice. Unfortunately, it is not possible to do exercises without access to some SAP system.September 20, 2023 at 1:41 am in reply to: Where do I get Change log with timestamps for sales order status changes? #48095
Please check tables VBUK and VBUP for other statuses like Delivery status, Billing status, Rejection status changes (header and item correspondingly).
In SAP, you can configure custom payment terms that match your installment schedule. These terms ensure that payments to the vendor are only released when certain conditions are met, such as the physical arrival of materials. This allows you to manage installment payments effectively while maintaining control over disbursements based on the agreed-upon milestones.
SAP FI Accounts Payable (AP) manages a company’s financial obligations to suppliers. It records vendor data, processes invoices, and handles payments. AP automates accounting entries, reconciles vendor accounts, and offers reporting tools. It integrates with other SAP modules and ensures compliance with tax regulations, streamlining vendor payment processes and financial control.
Please refer to the order management / billing documentation on the official SAP website: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISESeptember 9, 2023 at 9:18 pm in reply to: How to get actitivity details for every production version of the product #48022
To determine which activities are specific to which production version, you can use the common link between the MKAL and PLPO tables, which is typically the material number (product). You’ll need to join these tables based on the material number and plant. Once you have the relevant data, you can group by production version and calculate the total machine fix value for each production version.August 15, 2023 at 12:42 am in reply to: Condition records for the services of a Contract (Pricing) are not pulled #47892
In SAP, when pricing conditions are not being pulled for a contract service in transaction ME31K (create contract), several factors could be at play.
1. Ensure that the condition records you’ve created have valid dates that cover the period of the contract. Additionally, verify that the condition records are in an active state.
2. Check the service master data to ensure that the service you’re trying to add to the contract is correctly maintained. Verify that the service is assigned to the correct material group, and there are no inconsistencies in its configuration.
3. The condition records are accessed based on an access sequence defined in the pricing procedure. Ensure that the pricing procedure assigned to the contract contains the correct access sequence that references the required condition type and condition table for the service.
4. Verify the configuration of the condition type associated with the condition records. Check its settings for access sequence, calculation rule, and requirement. Incorrect configuration can prevent condition records from being pulled.
5. Confirm that the condition table used in the access sequence contains the necessary key fields to uniquely identify the service and other relevant criteria.
6. Review the pricing procedure assigned to the contract and check if it’s correctly linked to the condition types and access sequences needed for the service.
7. If you have any custom enhancements or modifications in place, they could potentially impact the retrieval of condition records. Review any custom code or configurations that might be affecting this process.July 27, 2023 at 6:30 pm in reply to: Maintenance plan due date and Basic finish date not matching. #47783
Here are some additional possibilities to consider:
Maintenance Plan Generation: Check how the maintenance plan was generated in SAP. If it is a dynamic plan based on equipment conditions or usage, it may lead to variations in the plan dates compared to static plans.
Maintenance Plan Priority: SAP allows you to assign priorities to maintenance plans. If other high-priority plans or work orders are taking precedence, it could delay the execution of the current maintenance plan.
Maintenance Plan Strategy: Different maintenance plan strategies (e.g., time-based, usage-based, condition-based) can have different triggers and scheduling mechanisms, which may cause variations in the plan dates.
Backlog of Orders: If there is a backlog of maintenance orders or work requests in the system, it could affect the scheduling of the current maintenance plan.
Dependencies on Materials or Spare Parts: If the maintenance plan is dependent on specific materials or spare parts, delays in the procurement or availability of these items could impact the execution dates.
Maintenance Plan Constraints: Check if there are any constraints or restrictions set in the maintenance plan that could affect the scheduling.July 20, 2023 at 1:26 am in reply to: SAP Document and Reporting Compliance – KSeF Poland #47680
Have you tried reaching out to SAP support? If you have followed the documentation and troubleshooting steps but are still unable to resolve the issue, it may be helpful to reach out to SAP support for further assistance. They can provide specific guidance and expertise related to the Document and Reporting Compliance tool and its integration with the KSeF platform.July 20, 2023 at 1:22 am in reply to: BIN inventory – last count date and historical ones #47677
In SAP, the LX03 transaction is used to display the stock situation for a particular storage type or warehouse number. It does not directly provide the option to view historical count dates or specify a time range. However, there are alternative approaches you can take to access historical count dates and filter the results based on a specific time range. Here’s how you can achieve that:
Transaction LX27: To view historical count dates, you can use the transaction code LX27. Enter the warehouse number and material or storage type, and execute the transaction. It will display a list of historical inventory documents with their respective count dates.
Inventory Management Reports: SAP provides several standard reports that allow you to analyze inventory and its history. Transaction codes like MB51 (Material Document List) or MMBE (Stock Overview) can provide historical information on inventory movements. By selecting the relevant filters and columns in these reports, you can retrieve the desired historical count dates.