Jump to content
Hellenic Glass Industry - Support portal

Search the Community

Showing results for tags 'mkdocs'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Categories

  • General
  • SD
  • FI-CO
  • PP-QM
  • MM-WM
  • PM

Calendars

There are no results to display.

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

Found 15 results

  1. Elias Stassinos
    Every customer can be assigned a text in the texts for the Sales Area: This text is automatically copied in the Sales Order Header Note 1 text, which then is printed in the Notes section of the invoice. Watch the short video for its use (click to enlarge):
  2. Elias Stassinos
    Customer Classification: TRADE NAME The TRADE NAME classification is added to 2 reports, ZHGI_CUSTOMERS_LIST, ZSD_BILLING_REPORT. If you use a layout and you cant find the filed add it. Screenshots: ZHGI_CUSTOMERS_LIST ZSD_BILLING_REPORT
  3. Elias Stassinos
    There are cases where we need to link products to external files. That could be desings , images (for web or any other usage). In order to be able to manage and automate processes the following rules must apply. NON-DECORATED: For files that refer to the piece of product the link will be the "Mould Code" that we have in SAP which is the first 5 digits of the code. Item: 23068-R66-FN00-SC01 Mould Code: 23068 For Files that need to refer to the final packaged code, we will use the whole SAP Code. Examples DECORATED: For decorated tableware products we will use the mould code plus the decoration code NON DECORATED TABLEWARE: For non decorated tableware we will use the 5 digit code of the mould. ***Important Note*** Any report/system/procedure that we will create will look at the rules above and assume that if a produt has an image , it will follow the above rules and at least will have the xxxxxxx-1.xxx as the first file.
  4. Elias Stassinos
    For Return Sales Orders of type ZREU, ZRE and ZRER we need to add a reason for the return The field is called ORDER REASON and some of you already use it. The list of reasons is the following: 901 Financial Reasons 902 Quality (curstomer claim) 903 Packaging Destroyed 904 Wrong Customer Order (Our responsibility) 905 Barcode Issue 907 Wrong Customer Order (Customer responsibility) If a reason is NOT defined the system will notify you upon pressing SAVE: ***IMPORTANT!!!*** If you press save the system will save the Order but you will NOT BE ABLE TO MAKE A BILLING. So you need to fill the order reason for all orders.
  5. Elias Stassinos
    Purpose: Every work order should have production and consumption during the month. Work Orders that have either only production or only consumption need to be checked for possible mistakes: Transaction: ZHGI_WO_CHECK Selection screen. We need to put the company (if BLANK then all companies will be checked), the year and the month The system will then show the orders that miss either consumptions or production. Clicking on the work order , will open the CO03 for further check of the order
  6. Elias Stassinos
    Apart from Glass Flow , we have some situations in production postings where we don't have any packed items but we have production of melted that becomes cullet. In these cases we need to: Calculate the amount of melted that we need to make cullet. Production of Cullet 531 to the work order of melted. After we calculate the melted = culllet we have to produce , we need to make a MIGO transaction with the following characteristics: Then you need to put the correct date and description. Also you need to delete the lines that the system brings automatically. These come from the BOM of Melted: Create a new line for cullet item And then put the necessary data: Item: R-2400302009 Quantity Plant Storage Location Order The final picture should be something like that: If all data are correct, then you only have to make a CHECK and then POST.
  7. Elias Stassinos
    If we want to fix also sale order quantity, then we fix also sales order quantity. In this step we can continue with sales order process. Next Step is to fix Warehouse. --Warehouse steps-- After the good issue from sales then in warehouse must have the following picture: In storage 916 and in delivery number storage BIN, we must have only the pallets that did not loaded. We must return from dummy BIN and PCs to normal Warehouse BIN with previous SU’s. When we complete the above values, we press Enter to go to next screen. This step must be per pallet. And a Transfer order have been created. If have not been confirmed. Then we confirmed it. We check the SU where have been gone. And we can move it with RF from BIN to BIN.
  8. Elias Stassinos
    In cases of Repack and Resort we may have some pieces of products that remain to storage locations 11xx and we need to send them for destruction. We must send them to Storage Location 0060 by using MIGO transaction. We run MIGO and use movement 311.
  9. Elias Stassinos
    In order to make the shipment document optional we have done the following: By default when creating a delivery for "CUS" it will not require a shipment document. If, for any reason (delivery grouping) you need to add a shipment document follow the steps described in the attached document (all you need to do is change the route from BGZZZZ to BG0000 for BG and UAZZZZ to UA0000 for Ukraine). HGI_SAP_SD_Shipment_Route_Change.pdf
  10. Elias Stassinos
    Transaction: ZHGI_PP_ACMON Purpose: You want to view the pallets as they are produced from barcode and are inputted to SAP. You can select to view the pallets based on the following selections: The posting date is the real production date while the date of manufacture follows the production rule where the pallets of Shift #3 are all registered to the previous day. This is used in production reports. After you run the report you can view/export/modify the view as you like: There is a column in the end of the Grid that shows any error message from the system, if there is any:
  11. Elias Stassinos
    Find below some of the most used transactions in SAP by Functional Area: COMMON MM03 - Display Materials BP - Display Customers / Vendors VCUST - Customer List MM60 - Materials List MKVS - List Of Suppliers SU53 - Authorization Check (When error occurs) SALES VA05 - Sales Order List with status and all info VA05 - Net Sales Reports and Lists VK13 - Display Conditions (Pricelists e.t.c) VF05 - Display Billing Documents (Invoices e.t.c) VL06 - Delivery Monitor VD53 - Display Customer/Material info VA33 - Display Scheduling Agreement VA35 - List of Scheduling Agreements VA45 - List of Sales Contracts Inventories/Warehouse LS26 - Warehouse Stock Overview per Material LS24 - Warehouse Stocks per Material LX02 - Warehouse Stock List MB52 - Warehouse Stocks on hand MB51 - Material Document List MMBE - Stock Overview MBGR - Material Documents by Movenent Reason MB5T - Stocks in Transit MB5TD - Stocks in Transit in Key Date BMBC - Batch Information for Material MSC3N - Display Batch LS27 - Display Storage Unit (SSCC) LT21 - Display Transfer Order LS03 - Display Storage Bin LX03 - Bin Status Report MB5B - Stock on Specific Date MBLB - Stocks on Subcontractor LX01 - List of Empty Storage Bins Purchasing ME51N - Create Purchase Requisition ME2N - Purchase Orders by PO ME23N - Display Purchase Order ME28 - Release Purchase Order by Code ME29N - Release Purchase Order (Single) ME5A - List Or Purchase Requisotions ME54N - Release Purchase Requisition ME55 - Collective Release of Requisitions ZHGI_CONTRACTS_V - Purchase Contracts (UA) ME2L - Purchase Orders by Supplier ME2M - Purchase Orders by Material ME48 - Display Quotation Production ZHGI_PP_ACMON - Pallets Produced by Barcode CR08 - Work Center Hierarchy Quality QA03 - Display Inspection Lot QA33 - Display Data for Inspection Lots QS26 - Display Characteristic Use QS36 - Display Inspection Method Use
  12. Elias Stassinos
    VA05 is normally used for Viewing Sales Orders. It has been modified to provide a general reporting for Net Sales. Note that in this transaction INTERCOMPANY are NOT included. It shows only Thirdparties Sales. In order to use it for Net Sales Reporting: Run VA05 Select a Variant for Sales. /HGI_LIST will display a general list like (old Sales Details EXCEL). The /HGI_REPORT1 is a simple report by Market Class and Sales Organization (company).: Select the Billing Date From/TO. BE CAREFUL NOT THE DOCUMENT DATE. Document date refers to SALES ORDER DATE: The /HGI_LIST output is like this: If you select the /HGI_REPORT1, the output is a report by Market Class and Sales Organization:
  13. Elias Stassinos
    Transaction: ZHGI_SD_SALESMAN1 Purpose: The report shows a list of all the customers assigned to one or more Salesman. Salesman can be selected on the selection screen. The report can be found in the User Menu like this: You can also run the report directly by writing the transaction in the command box and hitting enter. Selection: Salesman can be selected or it can be left blank to show all the salesmen with their customer data.
  14. Elias Stassinos
    If you cant see the transaction codes next to the menu Title then please follow the following procedure:
  15. Elias Stassinos
    For users that have the appropriate authorizations, have the capability to export the Sales Invoices to PDF files in their disk. Transaction: ZHGISD_LEGDOC_TO_PDF The manual of operations: HGI-IBM_SAP_SD_Mass_Export_to_PDF.docx
×
×
  • Create New...