API SD transition API July Pomida – Warehouse/PR creation Arnel Bon/Arnold Elpedez – PO creation/Material Master Ryan Marvin Entereso / Joy Pedraza – Circulation (Proj 8) Julius Segun / Orlando Pesigan – Logistics (Proj 8) Weng Dote – Customer master creation (Ad Sales/Prepress) Eden Argonza / Devonne Javier / Lorraine Garcia – Billing Grace Lopez / Noy Ramos – Internal Order creation Grace Bracero – Ad Sales Sales Order creation Amy Asis – Pre-press Sales Order creation Contact Persons Joy Aguila/Lonel Labit – Online Enterprise (OE) Cynthia Mendoza Clarence Dominguez/Stephen Soriano – SMOM, Policies Bayantel Proj. 8 shuttle service Van with ABS-CBN Publishing logo on front window 8:30 – MRT – Bayantel (B) 10 – 10:30 – B to ELJ 11 – 11:30 – E to B 11:30 – 12:30 – B to E 1:30 – 2:30 – B to E 2:30 – 3:30 – E to B 3:30 – 4:30 – B to E 4:30 – 5:30 – E to B 5:30 – 6 – B to E 6 – 6:30 – E to B 6:30 – 7 – B to MRT 7 – 7:30 – MRT to B 8 – 8:30 – B to E 8:30 – 9 – E to B 9 – 9:30 – B to E Organizational data Sales areas Company Code Client 2700 Client Sales Organization Circulation 1000 Distribution Channel Division P1 10 01 P2 20 02 A1 01 Sales Area 1 02 Ad Sales 2000 Pre-Press 3000 P3 10 10 P4 01 A2 02 A3 01 Sales Area 2 Sales Area 3 Customer Master Customer Master Data Definition: Customer Master Data - In the SAP System, all business transactions are posted to and managed in accounts. You must create a master record for each account that you require. The master record contains data that controls how business transactions are recorded and processed by the system. It also includes all the information about a customer that you need to be able to conduct business with him. Account Group - ensures that only the relevant screens and fields are displayed and ready for input for each of the customer’s different partner functions. For example, the address, communication, and bank data fields are omitted for the account group for one-time accounts. Customer Master Data General Data Address Control Data Marketing Contact persons Company Code Data Account Management Payment Transactions Correspondence Insurance Sales Area Data Sales Shipping Billing Partner Functions Output Account Group General data 3-series unique to API Name1 and Name2 Search term 1 & 2 Suffix CIRC, ADSL, PPRS Street, Street2, Street3 Determines route API0000028 -> API028 General data Contact person Can be set via VAP1/VAP2 also Company Code Data Default recon account Sales Area Data Sales Group AP1 – standard AP2 – consignment AP3 - complimentary Customer Group 01 Industry 02 Direct 03 Dealer 10 Advertiser 11 Agency 12 Government 13 Affiliated Company 14 Subsidiary Company 15 Blocktimer 16 TFCI Official 17 TFCI Personal 18 Tenants Z1 Print Z2 Subscription Z3 Bulk Subscription Z4 Bulk Sale Sales Area Data For Sales Org 2701, set relevant for POD. Sales Area Data Tax classification MWST 0 – tax exempt 1 – liable for taxes SPRO – Terms of Payment Partner Function Based on partner function rules User exit Project ZPARTNER INCLUDE ZXF04U01. Partner Function Rules Blocking customer Fill in blocks for selected sales area Customer deletion Selected sales area data Blocks the whole customer master data Watch-out From customer master data Menu Extras -> Classification Previous method for storing Partner functions? Some programs like ZO62 Sales invoice used the function CLAF_CLASSIFICATION _OF_OBJECTS – removed from ZO62 program. Customer Master Tables KNA1 – General data KNB1 – Company Code data KNVV – Sales Area data TCodes XD01/VD01 – Create XD02/VD02 – Change XD03/VD03 – Display XD99 – Customer Mass Maintenance VD05 – Block customer (Sales area) VD06 – Delete customer (Sales area) Material Master Material Master Material type ZPXD - API exdeal goods (Ex deal materials for SO) ZPSI - API stock inventory ZPNS - API non-stock inventory ZTRD - API retail inventory (circulation for SO) ZSER - FMS Services (ad sales/pre press materials for SO) Material Master OE Material Code Division A1 API Magazines A2 API Services A3 API Printing A4 API ExDeal Prod Hierarchy Z1 Current Magazine Z2 Back-Issue Magazine Z3 Regular Ads Z4 Advertorial Z5 Special Publication Z6 Inserts Weight for Shipping docs Additional Data - UOM Number of pieces of magazines per bundle (API Circulation provides the number of pcs.) - used in delivery receipt (ZO63) and BODR (ZO79) - basis of logistics of how many bundles to load in truck Basic Data 2 ISSN# aka Barcode - Used in delivery receipt - possible CRF – additional number at end for different batches Sales Org 1 Make sure to extend magazine materials ZTRD are extended for both distribution channels P1 and P2. Sales org 1 For magazines should link to PR00 condition for price Tax classification 0 – no tax 1 – liable for taxes ZTRD User Exit Sets material to batch management Valuation category to X – batch Transaction code CMOD, enter project name ZMM1. Component MGA00001. Include ZXMGOU02. Pricing/Discounts Pricing Material price Customer specific price Customer discount Rate customer discount – K007 Customer/Material discount – K005 Flat Material price Logistics\SD\Master Data\Conditions\Select Using Condition Type\Create (VK11) Enter Condition Type PR00 Click Key Combination button Select Material with release status. Enter. Enter the following: Sales org Distribution Channel Customer Valid on Valid to Material Amount/Rate Customer Discount Logistics\SD\Master Data\Conditions\Select Using Condition Type\Create (VK11) Enter Condition Type K005 or K007. Enter. Enter the following: Sales org Distribution Channel Customer Valid on Valid to Material (for K005) Amount/Discount in Percent ZT55 – Internal Order assignment by Material/Batch Batch Record MSC1N/MSC2N/MSC3N Auto-created from Goods Receipt Advance SODR loading/printing Manual creation of batch Proposal of Data to SO Customer Master Name Address Pricing Shipping Requirements Payment Terms Plant Sales Order Material Master Cost Plant Weight/Volume Availability Check TCodes MM01/MM02/MM03 – Material Master MM06 – Material deletion MMAM – change Material type VK11/VK12/VK13 – Condition/Discounts (K005/K007)/Price (PR00) VK31/VK32/VK33 – alternative Conditions/Discounts MSC1N/MSC2N/MSC3N – Batch Record ZT55 – Internal Order Assignment by Material/Batch SD Cycle 1. Inquiry 8. Payment (FI) 2. Quotation – could be used for pre-press 7. Billing 3. Sales Order 6. Post Goods Issue 4. Delivery 5. Picking/Packing Transaction Flow Purchase Req. Purchase Order OE Sales Order Outbound Delivery Billing (Sales Invoice) User Exits PO Creation – check Batch YYYYMM EXIT_SAPMM06E_016 MIGO GR – check Batch YYYYMM EXIT_SAPMM07M_003 Checks if plant 2700 and material group 240100N Does not check if batch is blank during PR Sales Orders Sales order documents Standard Order Order – Delivery - Invoice Consignment Order Fill-up – Issue - Invoice Consignment Processing: Customer consignment goods are goods which are stored at the customer locations but which are owned by your company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer usually returns consignment goods which are not required. Fill up is requested to move stock to customer special stock. Issue is initiated to bill the customer for stock used. Return is used to credit the customer for unused stock. Pickup is used to return the unused inventory into company unrestricted inventory. Complimentary – ZAP6 Complimentary Returns – ZAP7 Consignment Late Returns – ZRET API Returns – ZARE (not tested) Sales Order Flow ZAP3 ZAP4 ZAP3 ZAP5 ZAP4 BILLING ZARE ZAP1 ZAP2 ZAP6 ZRET ZAP7 OE Purchase ZR81 Order ZO27 OE ZO59 Sales Order ZR81 – Purchase order download ZO27 – OE to SAP Customer (OE02 interface) ZO59 – SODR – OE to SAP Sales Order Delivery Receipt Load (OE01 interface) Sample File format OE02 Interface 0|2700||2700|2701|P2|A1|0003|MICHAEL DUMLAO (DUMLAO MEDIA INC.)|MICH16CIRC||352779 Gananoque Drive, Missisauga, Ontario, L5N 2E4, Canada|0000|Metro Manila|PH|API0000117||||||||101030001|001|R1|MICH16CIRC|ZP01|2700|AP1|Z4|PHP|1|1|01|01|2 700|FOB|Free on Board|ZP01|01|0|Michael Dumlao|1||||Z1|27001273|Z2|27009991|||||||| OE01 Interface Print Order/Newstands/Consignment Fillup 10Q001CIRC,4590000000-PRINTORDER,01/08/2009,1ACT,1,200802 Reorder 10Q001CIRC,4590000000-REORDER,01/08/2009,1ACT,1,200802 Update PO 10Q001CIRC,4590000000-UPDATEPO,01/08/2009,1ACT,1,200802 Complimentary ADSA01CIRC,COMPLIMENTARY-API001,01/08/2009,1ACT,1,200802,Name,Address Bulk Subscription TVA01CIRC,SUBSCRIPTION,5/15/2009,1TBM,1,200906,Name,Address Regular Subscription 10Q001CIRC,PAID SUBSCRIPTION,01/08/2009,1ACT,1,200802,01/08/2010 ZO59 Reference PO# Determines which Storage location the Delivery uses Document Flow List of related documents that describes the history of a sales doc. Displays all preceding and subsequent documents. Can be viewed at header or item level Simplifies problem resolution Table VBFA Incompletion log Indicates fields that should be verified in order to consider the document complete. The log informs you of data which is missing in the document. A pop-up window is activated to tell you, when saving a document, that your data is incomplete. You can then either park the document or process it prior to saving. Tables VBAK, VBAP - SO VBUK/VBUP – status VBFA – doc flow ZBIADEF – Interface definition ZBIAEXE – last run date/time TCodes VA01/VA02/VA03 – Sales Order VA05 – List of SOs VA05N – ECC6 List of SOs Complimentary Zero net value issue DEVK951033 400 ECC6: Complimentary Zero Net Value Shipping Deliveries Auto-created from SO creation Contains quantity, delivery date, route, weight of delivery, storage location… Tables LIPS, LIKP Delivery Receipt VL71 – see printout Return Slip (RS) ZO58 – see printout Shipment Doc VT70 – see printout Proof of Delivery (POD) VLPOD VLPODL Shipping Point Determination – 2700 Route Determination Country and transportation zone Availability check Delivery date determination Tables LIKP, LIPS – delivery table ZONOUNITCOST – no display of unit cost for customers for DR TCodes VL01N/VL02N/VL03N – Outbound delivery VL71 – Print delivery receipt VLPOD/VLPODL – Proof of delivery VL06G – Post Goods Issue VL09 – Reverse Goods Issue VKM5 – Delete delivery/Reject SO VT01N/VT02N/VT03N – Shipment Doc VT70 – Print shipment doc ZT72 – no unit cost customers table maintenance ZO58 – Return Slip (RS) Billing BIR permit # 0508-116-00057-CBA/A Billing Methods Can be done differently for each customer Per shipment Periodically (e.g. monthly) Collectively (e.g. every P100,000) Sales Order Delivery Sales Order Delivery Delivery Sales Order Sales Order Invoice Collective Delivery Invoice Invoice Invoice Split Delivery Invoice Individual Automatic Account Assignment SD/Basic Functions/Account Assignment ERL – Revenue, ERS – Sales Deductions, MWS – Tax When in billing doc, go to environment\Account determination analysis. Tables VBRP – sales invoices TCodes VF01/VF02/VF03 – Billing VF05 – Billing doc list VF05N – ECC6 Billing doc list VF04 – batch job VF11 – Cancel billing Credit Management Credit Checking Credit exposure is a total combined value of: Open Orders Open Deliveries Open Billing Documents Open items (accounts receivable) Can define whether an error or a warning message appears Can be initiated at: Sales order creation Delivery creation Post Goods Issue (Shipping confirmation) Credit Management Customer Credit Management (FD32) Enables you to minimize the credit risk yourself by specifying a specific credit limit for your customers. Thus you can take the financial pulse of a customer or group of customers, identify early warning signs, and enhance your credit-related decision-making. This is particularly useful if your customers are in financially unstable industries or companies, or if you conduct business with countries that are politically unstable or that employ a restrictive exchange rate policy. TCodes FD32 – Credit Mgmt F.31 – Credit Overview report Logistics Information System (LIS) LIS Sales IS Purchasing IS Production IS Logistics Information System Plant Maintenance IS Inventory Management IS Quality Management IS Sales Information System SIS is: Used to display sales results and perform functions such as budgeting, rebate, planning, forecasting… Downloaded to spreadsheets. Used to perform sales history/budget loads Uses Information structures that are updated from sales transactions. Each IS forms its own database table IS are historical files S901 S902 S910 S911 ABS-CBN Mthly Revenue Report ABS-CBN Daily Revenue Report API Monthly Revenue Report API Daily Revenue Report Sales Orders Information Structure Deliveries Invoices Review Configure System Enter Master Data Enter Business Transactions Populate Sales Information System Organizational data Master data Material Master Customer Master Sales Orders Shipping Transaction data Pricing Billing On-line up-to-date sales information Effects of Sales Cycle on G/L account SD transaction Effect in FI Sales Order Effect in MM Purch Req MRP Post Goods Issue Reduces stock quantity and value Billing DR – Customer (A/R) CR – Revenue Customer Payment DR – Bank CR – Customer (A/R) SD integration points with FI/CO Inquiry Quotation Contract SO Delivery Shipment Document Goods Issue Customer Invoice SD Credit Info Preliminary Costing Inventory Valuation Profitability A/R FI/CO Credit information: When SO is created, SAP checks the credit information (entered in FI) to confirm that the order is within the specified credit limit. Inventory valuation: When a good is issued, it is taken out of inventory and therefore will affect the inventory valuation in FI. Profitability and A/R: When the customer invoice is issued, a direct posting will be made in FI to A/R and later, when payment is received, to profitability. SD integration points with MM/PP Inquiry Quotation Contract SO Inventory Availability Delivery Independent Requirements Product Info Requisitions Master Scheduling Shipment Document Goods Issue Inventory Info Customer Invoice MM/PP SD Product information: When a SO is created, the product information from MM is reflected within (eg. Name of material, unit of measure…) Requirements: When a SO is created, it immediately looks to MM to confirm schedule lines and quantities. Inventory Information: When a delivery document is created, a commitment is made in MM in inventory. When the goods are issued there is an automatic decrease in inventory. API Security Roles Z:API_SD_DELIVERY Z:API_SD_LOGISTICS Z:API_SD_BILLING Z:API_BILLING_MANAGER Z:API_SD_MASTER_DATA_CREATION Pending/To-do USD on sales order Use of USD (other currency) on sales order Used PHP equivalent at the moment. Customer master should have currency: USD on sales area/sales tab. Sales invoice (ZO62) needs to reflect currency instead of default “Total PHP”. Contact: Devonne Javier Magazine Volume number Regular magazines – YYYYMM (Batch) – monthly release Special magazines – Volume # 1.1 – release varies within the year Proposal: use ZT55 – to indicate volume number for each material/batch Double check on storage location for ZO59 Affected: DR Possible: BCSR, sales invoice, credit memo, return slip, BODR, sell thru Contact: Ryan Marvin Entereso Expiration date on DR Regular subscriptions should show Expiration date and Remarks as PAID SUBSCRIPTION. BODR enhancement Creation date of delivery Double check address (remove Metro Manila) Partner Function Z2 - Sales Representative name (between previous account and customer name) VT70 – Shipment doc MAIN2 window of ZO67 (Summary) list – single space Create new page if more than allocated space Summary Contact: Julius Segun Sales Invoice Total PHP to Total <currency> ATTN: <contact person> Tax inclusive for Pre-press Calculation of tax is via condition type MWST. Currently calculation is tax exclusive. Workaround is being done by Amy Asis at the moment. ZO70 – Credit Memo Add customer # Hide VAT if PHP 0.00 (FI – Alma) – doc type DM, DG SD – doc type RV Contact: Devonne Javier Pre-press Job out Cost Report Contact: Amy Asis Monthly report with job out cost Pre-press Unbilled JOs and QCs JO – job order QC – quotation contract Contact: Amy Asis For Research Customer Rebate (Eden) Collective Bulk discount (Ryan/Dev)