snc100 6 invoice collaboration

Unit 5Invoice Collaboration in SAP SNC

Unit OverviewIn this unit, you will gain deeper insight into the invoice collaboration with SAPSNC.

Unit ObjectivesAfter completing this unit, you will be able to:

Explain invoice collaboration within SAP SNC Perform invoice collaboration in SAP SNC Customize invoice collaboration in SAP SNC Set up message determination for invoice collaboration

Unit ContentsLesson: Invoice Collaboration Process Overview ... . . . . . . . . . . . . . . . . . . . . . . .208Lesson: Process Demo: Invoice Collaboration ... . . . . . . . . . . . . . . . . . . . . . . . . . .223

Exercise 6: Invoice Processing with SAP SNC... . . . . . . . . . . . . . . . . . . . . . .225Exercise 7: Self-Billing with SAP SNC.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

Lesson: Relevant Customizing for Invoice Collaboration in SAP SNC ..237

2009 2009 SAP AG. All rights reserved. 207

Unit 5: Invoice Collaboration in SAP SNC SNC100

Lesson: Invoice Collaboration Process Overview

Lesson OverviewIn this lesson, you will learn about invoice collaboration within SAP SNC.

Lesson ObjectivesAfter completing this lesson, you will be able to:

Explain invoice collaboration within SAP SNC

Business Example

BackgroundInvoice collaboration enables a supplier or customer to produce invoices for goodsthat have been provided by the supplier to the customer. You can create invoicesfor purchase orders, replenishment orders, or advanced shipping notifications(ASNs).

Note: ASNs are related to a purchasing document, such as a purchaseorder or scheduling agreement.

Invoice collaboration in SAP SNC supports the following processes:

The supplier manually creates an invoice in SAP SNC for goods that he orshe has provided to the customer.

The supplier sends an invoice via XML message through SAP NetWeaver toSAP SNC.

Caution: The IDocs, XML messages, and mappings dependon which ERP system and release is being used. Mappings aresometimes required for the message flow between the supplierssystem and SAP SNC. Since the mappings are dependent on thesuppliers system, they cannot be predefined in the SAP SNCstandard delivery. You must create the mappings as part of a projectsolution.

The supplier manually creates a subsequent debit or credit in SAP SNC. The supplier sends a subsequent debit or credit via XML message through

SAP NetWeaver to SAP SNC.

Caution: The IDocs, XML messages, and mappings dependon which ERP system and release is being used. Mappings aresometimes required for the message flow between the suppliers


SNC100 Lesson: Invoice Collaboration Process Overview

system and SAP SNC. Since the mappings are dependent on thesuppliers system, they cannot be predefined in the SAP SNCstandard delivery. You must create the mappings as part of a projectsolution.

Hint: In all of the above processes, SAP SNC is able to receive aninvoice confirmation from the customers back-end system after invoiceverification. However, the use of this function is dependant on thecustomer back-end system being able to send such a confirmation.

The customer creates a self-billing invoice, which is sent to the SAP SNCsystem.

The customer creates a self-billing invoice, which is sent to SAP SNC andthe suppliers ERP system.


The customer performs a revaluation. The created documents are sent tothe SAP SNC system.

The customer performs a revaluation. The created documents are sent toSAP SNC and the suppliers ERP system.


DefinitionsInvoice

An invoice is created by the supplier to charge a customer for goods thathave been provided by the supplier to that customer.An invoice can reference an existing purchase order, replenishment order,or advanced shipping notification (this allows you to invoice a schedulingagreement).



Self-billing invoiceA self-billing invoice is created by a customer. It contains the invoice detailsfor goods provided by the supplier to the customer. A supplier does notcreate an invoice for goods that are invoiced using a self-billing invoice.A self-billing invoice references an existing purchase order, replenishmentorder, or advanced shipping notification (this allows you to invoice ascheduling agreement).

Subsequent debit/creditThis is an additional document that the supplier creates for a transactionthat has already been invoiced. The subsequent debit or credit charges anadditional value for, or reduces the original value of, a quantity of goods thathas already been invoiced.A subsequent debit or credit can reference an existing purchase order,replenishment order, or advanced shipping notification.

RevaluationIf the price of a product changes and is retroactively valid, the customercan create a revaluation. This determines the difference in value for itemsthat have already been invoiced. A revaluation can only be created for apurchasing order or advanced shipping notification that has the Evaluatedreceipt settlement (ERS) indicator set.

Master Data and Settings for InvoicesTo use the invoice collaboration functions in SAP SNC, you must set up therequired master data in SAP SNC. In addition to general master data for suppliercollaboration in SAP SNC, you must also set up invoice-specific master data.



Partner-dependent purchasing document dataYou can transfer partner-dependent purchasing document data from SAPERP to SAP SNC using the Core Interface (CIF). If you do not havethis functionality set up, or you want to change this data, you can enterpurchasing document master data manually in SAP SNC.You can maintain partner-dependent master data using the SAP SNCWeb UIby choosing Master Data Partner-Dependent Data Maintenance ofPartner-Dependent Purchasing Document Data. You can also access it fromthe SAP Easy Access screen by choosing Supply Network CollaborationMaster Data Application-Specific Master Data Invoice MaintainPartner-Dependent Purchasing Document Data. Both the customer andsupplier can maintain purchasing document data in the customers SAPSNC system.You must specify the following data:

Customer number Purchasing document number Purchasing document type Purchasing document itemYou can manually maintain the following data:

Net price Price unit Price unit of measure Terms of payment key Incoterm Incoterm location Tax code Jurisdiction code Currency Use Data to Create Invoice indicator

If you select the Use Data to Create Invoice indicator, SAP SNC usesthis data to automatically fill out the corresponding fields when thesupplier creates an invoice.



Partner-dependent payment termsYou can maintain partner-dependent payment terms using the SAP SNCWebUI by choosing Master Data Partner-Dependent Data Assignmentof Payment Terms to Partners. You can also access it from the SAP EasyAccess screen by choosing Supply Network Collaboration Master Data Application-Specific Master Data Invoice Assign Payment Termsto Partners.This enables the customer or supplier to maintain the payment terms fora particular supplier-customer pair.You can maintain the following data:

Terms of payment Net payment period Payment period for normal cash discount in days Normal cash discount percentage Payment period for maximum cash discount in days Maximum cash discount percentageSAP SNC uses this data to automatically assign the defined payment termswhen you create an invoice for the specified partner. If you want to usedifferent payment terms for a particular invoice, you can manually overwritethe payment terms in the invoice.

Tax codesTo send calculated tax data between SAP SNC and the customers back-endERP system, you must maintain tax codes in both SAP SNC and SAP ERP.This is because SAP ERP uses the tax code to calculate the gross amount.Each tax code can relate to a number of tax rates that you maintain.

Note: For more information about maintaining tax codes, see theImplementation Guide (IMG) for Supply Network Planning bychoosing Invoice Maintain Tax Codes for Invoices.



Data transferred via CIFIf you are using an SAP ERP 2005 or higher back-end system, you cantransfer the following data via the Core Interface (CIF) from purchasingdocuments (scheduling agreements and contracts) in SAP ERP to SAP SNC.If you transfer this data using CIF, you do not need to maintain it manually inSAP SNC.

Payment terms Document currency Goods receipt based invoice verification indicator Evaluated receipt settlement indicator No cash discount indicator Price Price unit Purchase order price unit Conversion of order price unit to order unit Conversion of order unit to base unit Invoice receipt indicator Incoterms Incoterm location Jurisdiction code Final invoice indicator Tax code

Incoterms in SAP SNCWhen an invoice is created, the Incoterm and location that are used in thereference document are transferred from that reference document to theinvoice.The master data for Incoterms in the customers back-end system, however, isnot transferred to SAP SNC. Therefore, you must manually maintain masterdata for Incoterms in your SAP SNC system so that it matches the Incotermsin your back-end ERP system. If, in an invoice, you use an Incoterm thatyou have not maintained in the master data, the system generates an errormessage when it performs validation checks for the invoice.Define Incoterms in Customizing for SAP SNC by choosing SCM BasisMaster Data Define Incoterms.



Invoice AlertsYou can view invoice-relevant alerts in the new Invoice alert category of the AlertMonitor. As of SAP Supply Network Collaboration (SAP SNC) 7.0, the followingalert types are available:

Exception in Invoice Validation(7130)

This alert indicates an exception in the validation of an invoice.

Payment Past Due (7131)

This alert indicates that the due date for payment of an unpaid publishedinvoice has passed. This alert is generated by the Generate Alerts forInvoices (/SCA/INVOICE_ALERT) report. When a payment notification isreceived in SAP SNC, the system deletes any Payment Past Due alert thatexists for the corresponding invoice.

The payment due date is the Baseline Date plus the Net Payment Periodspecified in the invoice header. When the system determines the paymentdue date, if no Net Payment Period has been specified, the system uses theNormal Cash Discount period instead. If this period is also not specified, thesystem uses the Maximum Cash Discount period.

If none of these payment periods have been specified, the system does notcreate an alert.

Invoice Follow-Up-Requirement CodeWhen a customer sends a purchase order to SAP SNC, the XML message includesa follow-up-requirement code relevant to invoicing. This determines whetherthe supplier needs to create an invoice for the purchase order or not. Thisinvoice-relevant follow-up-requirement code has three possible values that definewhether the creation of an invoice is mandatory, not allowed, or optional.

Hint: If you use a purchase order sent from an SAP ERP back-endsystem as the reference document for your invoice, the purchase ordermust have been sent to SAP NetWeaver XI using an IDoc of typePORDCR1.PORDCR102 in order for the follow-up code to have beensent. IDocs of type ORDERS.ORDER05 do not transfer the invoicefollow-up code.

If you want to create an invoice for a scheduling agreement (using anASN) the invoice follow-up code is transferred via the Core Interface(CIF).



XML Messages for Invoice CollaborationInvoice collaboration in SAP SNC uses the following XML messages:

InvoiceRequest

If the customer creates a self-billing invoice or revaluation in his orher back-end system and the customer creates an IDoc message of typeGSVERF.GSVERF03 for customer self-billing or the revaluation of aninvoice in his or her back-end system he or she sends this message toSAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI). SAPNetWeaver XI maps the message to an InvoiceRequest XML messageand sends it to SAP SNC. SAP SNC uses this message to create aself-billing invoice or revaluation.

When the supplier publishes an invoice in SAP SNC, SAP SNC sendsan invoice request to the customer's back-end ERP system via SAPNetWeaver XI using an XML message of type InvoiceRequest.

InvoiceConfirmation

If a customer confirms an invoice in his or her back-end system,SAP SNC can receive this confirmation as an XML message of typeInvoiceConfirmation. SAP SNC uses this XML message to update thestatus of the invoice.

Hint: Although SAP SNC supports this function, the ability to makeuse of it is dependent on the customers back-end system being ableto create such a confirmation.

PaymentAdviceNotification

When the customer creates a payment run in his or her back-end system,a remittance advice is sent to SAP NetWeaver XI using an IDoc of typeREMADV.PEXR2002. SAP NetWeaver XI maps this IDoc to an XMLmessage of type PaymentAdviceNotification and sends it to SNC. SAP SNCuses this XML message to update the payment status of the invoice.

Manual Creation of Invoice Using the SAP SNC Web UIThe supplier can create an invoice using the Create Invoice screen.



The supplier can create the following types of invoice:

Standard invoice Subsequent debit Subsequent credit

Note: You can only create subsequent debits and credits for referencedocument items that have already been invoiced. The validation checkINV_ITM_CREDIT_QTY checks that the subsequent debit or creditquantity does not exceed the quantity that was invoiced.

When you create an invoice, you can reference a purchase order item or anadvanced shipping notification (ASN) item. If a purchase order item also hasan associated ASN, you can only reference the purchase order item or the ASNitem, not both.

When the supplier creates an invoice, SAP SNC checks the Invoice CreationType field in the reference document. The following three settings are availablein this field:



InvoiceCreationType

Description

InvoiceCreation withPurchaseOrderReference

The system sets this value as follows:

In the standard setting, this is the default value for apurchase order or replenishment order that has beencreated without the Goods Receipt-Based InvoiceVerification indicator set.

This setting is controlled by the validation checkPO_INVOICE_CREATION for purchase orders, andRO_INVOICE_CREATION for replenishment orders.

If a purchase order item or replenishment order item hasalready been partially invoiced using the purchase orderas the reference document.

If this value is the status of the Invoice Creation Type field, aninvoice can only be created for this reference document item byusing the purchase order as the reference document.

InvoiceCreationwith ASNReference

The system sets this value as follows:

In the standard setting, this is the default value fora purchase order that has been created with theGoods-Receipt-Based Invoice Verification indicator set.

This setting is controlled by the validation checkPO_INVOICE_CREATION for purchase orders, andRO_INVOICE_CREATION for replenishment orders.

If a purchase order item has already been partially invoicedusing the ASN as the reference value.

If the Invoice Creation Type field has this value, an invoice canonly be created for this purchase order item by using the ASNas the reference document.

InvoiceCreationSimilar toPredecessorInvoice

If the Invoice Creation Type field has this value, an invoice canbe created using either the purchase order or the ASN as thereference document. Any subsequent invoices created for thatsame item, however, must use the same reference documenttype.For example, if part of purchase order item 10 is invoicedusing an ASN as the reference document, then any subsequentinvoices for purchase order item 10 must also use ASNs as thereference document type.It is possible to configure SAP SNC to make this thedefault value for purchase order items and ASN items,regardless of the Goods-Receipt-Based Invoice Verificationindicator. To do this, you must activate the validation checkPO_INVOICE_RELATED_TO_PO_OR_ASN for purchaseorders and RO_INVOICE_RELATED_TO_PO_OR_ASN forreplenishment orders. If you set these validation checks asActive, you must also make sure that the validation checksPO_INVOICE_CREATION and RO_INVOICE_CREATIONare Inactive.



Invoice with Reference to Purchase Order or Replenishment Order ItemAn invoice can only be created with a purchase order as the referencedocument if the Invoice creation type field in the purchase order item datahas the status Invoice Creation with Purchase Order Reference or InvoiceCreation Similar to Predecessor Invoice.An invoice can be created for a valid purchase order.When the invoice is created, the PO item is updated:

Item Creation TypeThis field is updated with the status Invoice Creation with PurchaseOrder Reference.

Quantity to Be InvoicedThis is the remaining quantity that is to be invoiced.

Invoiced QuantityThis is the total invoiced quantity relating to this purchase order.

Invoice with Reference to Advanced Shipping Notification ItemAn invoice can be created for a valid scheduling agreement or purchase orderby using an associated ASN as a reference document.An invoice can only be created with an ASN as the reference document if theInvoice Creation Type field in the item data has the status Invoice Creationwith ASN Reference or Invoice Creation Similar to Predecessor Invoice.When the invoice is created, the ASN item (and any associated PO item)is updated:

Item Creation TypeThis field is updated with the status Invoice Creation with ASNReference.

Quantity to Be InvoicedThis is the remaining quantity that is to be invoiced.

Invoiced QuantityThis is the total invoiced quantity relating to this purchase order item orscheduling agreement item.

Invoice Creation Using XML Message from SupplierBack-End SystemIf the suppliers back-end system is connected to the customers SAP NetWeaverXI system, it is possible for the supplier to create a new invoice in his or her ownback-end system and send an invoice request to SAP NetWeaver XI using an XMLmessage of type InvoiceRequest or an IDoc of type INVOIC.INVOIC01.



Caution: Note that the IDocs, XML messages, and mappings depend onwhich ERP system and releases are being used. Mappings are sometimesrequired for the message flow between the suppliers system and SAPSNC, depending on the suppliers system. Since the mappings aredependent on the suppliers system, they cannot be predefined in theSAP SNC standard delivery. You must create the mappings as part of aproject solution.

The following processes are then possible:

The customers SAP NetWeaver XI system receives an XML message oftype InvoiceRequest or an IDoc of type INVOIC from the supplier. Fromhere an XML message of type InvoiceRequest is sent to SAP SNC, and anIDoc of type INVOIC is sent to the customers ERP system.

The customers SAP NetWeaver XI system receives an XML message oftype InvoiceRequest from the supplier. SAP NetWeaver XI sends an XMLmessage of type InvoiceRequest to SAP SNC, where the invoice is checkedagainst validation checks. If the invoice passes the validation checks, itis automatically published and sent on from SAP SNC to the customersSAP ERP system via SAP NetWeaver XI. If the invoice does not pass thevalidation checks, it is given the status Received. In this case, the suppliermust manually change and publish the invoice in SAP SNC in order for itto be sent on to the customers SAP ERP system.

Creation of Self-Billing InvoiceThe customer can create a self-billing invoice in his or her ERP back-end systemand send an IDoc of type GSERVF.GSERVF03 to SAP NetWeaver XI. SAPNetWeaver XI maps this to an XML message of type InvoiceRequest. Whenthe self-billing invoice is received in SAP SNC, SAP SNC performs a series ofvalidation checks to ensure that the correct data is filled out and that the datais consistent.

When a self-billing invoice is created, SAP SNC fills the Invoice Type field withthe value Self-Billing Invoice and assigns the status Published. Self-billinginvoices cannot be changed in SAP SNC.

Creation of RevaluationThe customer can create a revaluation for a self-billing invoice in his or herERP back-end system and send an IDoc of type GSERVF.GSERVF03 to SAPNetWeaver XI. SAP NetWeaver XI maps this to an XML message of typeInvoiceRequest and sends it to SAP SNC. When SAP SNC receives this messageand creates a revaluation, it fills the Invoice Type field with the value Self-Billing



Invoice and assigns the status Published. Depending on the action code in themessage, the Item Type field is either assigned the value Revaluation Creditor Revaluation Debit.

Invoice PublicationTo support invoice processing in the customer back-end system, you must sendinvoices created in SAP SNC to the customer back-end system. Do this by sendingan XML message of type InvoiceRequest.

In the standard setting, invoices are automatically sent in the background whenyou call the publish function. This can be carried out in the following ways:

Validation Check

In the standard setting, SAP SNC sends the XML messages directlyin the background. This is controlled by the validation checkINV_PUBLISH_DIRECT.

If you deactivate this validation check, SAP SNC sends the XML messagesusing the Post Processing Framework (PPF).

Post Processing Framework (PPF)

If you want SAP SNC to send the XML messages using the PPF, you mustalso activate actions in the /SCA/BOL_INVOICE PPF action profile for the/SCA/ICH application as follows:

To send XML messages of type InvoiceRequest to thecustomer back-end system when you call the publish functionfrom the Create Invoice screen, you must activate the action/SCA/BOL_INVOICE_XML.

If you want SAP SNC to automatically send an XML message of typeInvoiceRequest to the customer back-end system for a valid invoicethat was received in SAP SNC from a supplier back-end system, youmust activate the action /SCA/BOL_INVOICE_XML_ROUTING.

Invoice StatusSAP SNC sets the status of an invoice to show which stage of the invoice processthe invoice is currently at.



Invoice StatusStatus Triggering FunctionDraft The supplier saves the invoice as Draft. SNC does not

send out invoices saved with the status Draft. Use thisstatus if the invoice is incomplete.

Published The invoice is published. The supplier can no longer makechanges to the invoice.

Received The supplier sent the invoice via XML to SAP SNC. SAPSNC has not published the invoice.

Paid This status is set by the XML message of typePaymentAdviceNotification which is received from thecustomer back-end system when a payment run has beencompleted.

Acceptance Status

If the customer sends an invoice confirmation from his or her back-end systemusing an XML message of type InvoiceConfirmation, this status is set. Thefollowing status values are available:

Status Triggering FunctionPending The customer has not yet confirmed or rejected the

invoice.Accepted The customer back-end system accepted the invoice and

sent an XML message of type InvoiceConfirmation.Rejected The customer back-end system rejected the invoice and

sent an XML message of type InvoiceConfirmation.



Lesson Summary

You should now be able to: Explain invoice collaboration within SAP SNC


SNC100 Lesson: Process Demo: Invoice Collaboration

Lesson: Process Demo: Invoice Collaboration

Lesson OverviewThis is your chance to see what has been discussed and to view a systemdemonstration.


Perform invoice collaboration in SAP SNC

Business Example

Demo

Figure 57: Demo



Exercise 6: Invoice Processing with SAPSNC

Exercise ObjectivesAfter completing this exercise, you will be able to: Run an invoice processing scenario with SAP SNC

Business ExampleYour supplier creates an invoice in SNC with reference to a purchase order. Onpublication, the invoice is sent to the ERP system, where it is verified and thepayment run is carried out. The payment information is sent to SNC and the statusof the invoice is updated accordingly.

Task 1: Create an invoice in SAP SNCLog on to the supplier view with supplier user IU-SUPA## and call up thepurchase order you created in the Purchase Order Collaboration exercise. Ifnecessary, create a new purchase order in ERP for this exercise. Create an invoice,INV_##, directly from the Purchase Order Details screen.

Note: In a real-world scenario, the supplier might want to create aninvoice for several positions. In this case, the Documents RequiringInvoices function provided from the Invoice menu is an efficient way toaccomplish this task. Feel free to explore this as an alternative to creationvia the Purchase Order Details screen.

1. Log on to the supplier view with supplier user IU-SUPA## and call up thepurchase order you created. If necessary, create a new purchase order in ERP.

2. Create an invoice, INV_##, directly from the Purchase Order Details screen.

Task 2: Display the invoice in the ERP systemDisplay the invoice in the ERP system

Hint: This task is performed in the role of the customer thus you need touse user SNC100-## to log on to the ERP system.

1. Display the invoice in the ERP system.

Continued on next page



Task 3: Release the invoiceRelease the invoice

1. Release the invoice in the SAP ERP System.

Task 4: Conduct the payment runConduct the payment run

1. Conduct the payment run.

ResultThe payment information has been sent to SNC. You can check in transactionWE05 to ensure that an IDoc of the type REMADV.PEXR2002 has been sent.

Task 5: Check the status of the invoice in SNCWhat is the status of the invoice in SNC following the payment of the invoice?

Hint: This task is again performed in the role of the supplier. (UserIU-SUPA##).

1. Check the status of the invoice in SNC.



Solution 6: Invoice Processing with SAPSNCTask 1: Create an invoice in SAP SNCLog on to the supplier view with supplier user IU-SUPA## and call up thepurchase order you created in the Purchase Order Collaboration exercise. Ifnecessary, create a new purchase order in ERP for this exercise. Create an invoice,INV_##, directly from the Purchase Order Details screen.

Note: In a real-world scenario, the supplier might want to create aninvoice for several positions. In this case, the Documents RequiringInvoices function provided from the Invoice menu is an efficient way toaccomplish this task. Feel free to explore this as an alternative to creationvia the Purchase Order Details screen.

1. Log on to the supplier view with supplier user IU-SUPA## and call up thepurchase order you created. If necessary, create a new purchase order in ERP.

a) Navigate to the Purchase Order Details screen by choosing PurchaseOrder Purchase Order Details.

b) Enter your PO number and choose Go, or use the input help to findthe PO.

2. Create an invoice, INV_##, directly from the Purchase Order Details screen.

a) Choose Create Invoice for Items. You branch to the invoice creationscreen.

b) On the Create Invoice screen, enter an invoice number, INV_##, andchoose Check.

c) If the check is okay, choose Publish to send the invoice to the ERPsystem.




Task 2: Display the invoice in the ERP systemDisplay the invoice in the ERP system

Hint: This task is performed in the role of the customer thus you need touse user SNC100-## to log on to the ERP system.

1. Display the invoice in the ERP system.

a) In the ERP system, choose Logistics Materials ManagementLogistics Invoice Verification Further Processing InvoiceOverview or use transaction code MIR6.

b) On the selection screen, enter the following parameters and choose(F8):Company code: 1000Invoicing Party: SNC100A-##Entry type: select EDIInvoice status: select all checkboxes

Hint: Ensure that the Processor selection field is empty.

The system shows a list of invoice documents. Choose Display Detailsto view the details.

Task 3: Release the invoiceRelease the invoice

1. Release the invoice in the SAP ERP System.

a) In the ERP system, choose Logistics Materials ManagementLogistics Invoice Verification Further Processing ReleaseBlocked Invoices or user transaction code MRBR.

b) On the selection screen, enter the following parameters and press(F8):

Company code: 1000Vendor: SNC100A-##

c) The system lists the invoice you created in SNC as the supplier. Selectthe corresponding line and choose Release Invoice .

d) Choose Save . The invoice is now released for payment.




Task 4: Conduct the payment runConduct the payment run


a) In the ERP system, choose Accounting Financial Accounting Accounts Payable Periodic Processing Payments or usetransaction code F110.

b) On the selection screen, make the following entries:Run date: Todays dateIdentification: SNC##

c) Go to the Parameters tab page and enter the following:Company code: 1000Pmt mthd: UNext p/date: today + 2 monthsVendor: SNC100A-##

d) On the Additional Log tab page, make the following entries:

Due check date:Pmnt method selection if not successful:Line items of the payment documents:Vendors (from): SCN100A-##Vendors (to): SCN100A-##

e) On the Print/data medium tab page, make the following entries:

Enter the variant for the program RFFOAVIS_FPAYM: SNC100

f) Switch back to the Status tab page and save your entries.

g) Choose Payment run to execute the payment run, and confirm anywarning messages with Yes.

h) In the dialog box to schedule and start the payment run, make thefollowing entries:

Start date: todays date

Start immediately:

Create pmnt medium:

Choose Enter to start the payment run.

i) Choose Status repeatedly until the status is

Posting orders: 1 generated, 1 completed.




ResultThe payment information has been sent to SNC. You cancheck in transaction WE05 to ensure that an IDoc of the typeREMADV.PEXR2002 has been sent.


Hint: This task is again performed in the role of the supplier. (UserIU-SUPA##).

1. Check the status of the invoice in SNC.

a) Log on to SNC as the supplier (IU-SUPA##) and choose InvoiceInvoice Overview. Choose Go to display your invoices. Your invoiceshould now have the status Paid.

b) Click the invoice number to branch to the Invoice Details screen. Onthe Payment status tab page, you can see the date and amount of thecustomer payment.



Exercise 7: Self-Billing with SAP SNC

Exercise ObjectivesAfter completing this exercise, you will be able to: Run a self-billing scenario with SAP SNC

Business ExampleIn this process, the customer creates an invoice for goods that have been purchasedfrom a supplier.

The responsibility for creating an invoice does not lie with the supplier; however,the supplier is able to view invoices once the customer has sent them to SAP SNC.The supplier can also view the status of a payment run for an invoice, that is, oncethe customer has initiated and completed the payment run.

When the customer purchases goods from a supplier, he or she can issue aninvoice, thus shortening the time of document creation. The customer can theninitiate payment for that invoice.

Task 1: Carry out invoice verificationCaution: As a prerequisite to this scenario, you must have completed theexercise on release processing and must have created a correspondingASN for at least one schedule line for which you have posted the goodsreceipt in ERP.

Hint: This task is performed in the role of the customer (UserSNC100-##) in the ERP system.

1. Carry out an invoice verification run in ERP.

2. Write down the resulting invoice number. ______________________

Task 2: Display the invoice in SNCLog on as the supplier and display the invoice in SNC.

Hint: This task is performed in SNC. Since the invoice is related to theASN for the scheduling agreement release, you need to log on as supplierSNC100B-## using the user IU-SUPB##.

1. Log on as the supplier and display the invoice in SNC.




Task 3: Conduct the payment runConduct the payment run.

Hint: This is again a task for the customer to be carried out in ERP withuser SNC100-##.


ResultThe payment information has been sent to SNC. You can check in transactionWE05 to ensure that an IDoc of the type REMADV.PEXR2002 has been sent.


Hint: This finally is a task performed by supplier SNC100B-## (UserIU-SUPB##) in SAP SNC.

1. Check the status of the invoice in SNC



Solution 7: Self-Billing with SAP SNCTask 1: Carry out invoice verification

Caution: As a prerequisite to this scenario, you must have completed theexercise on release processing and must have created a correspondingASN for at least one schedule line for which you have posted the goodsreceipt in ERP.

Hint: This task is performed in the role of the customer (UserSNC100-##) in the ERP system.

1. Carry out an invoice verification run in ERP.

a) In the ERP system, choose Logistics Material ManagementLogistics Invoice Verification Automatic Settlement EvaluatedReceipt Settlement or use transaction code MRRL.

b) On the selection screen, enter the following parameters:Company Code: 1000Vendor: SNC100B-##Purchasing document: scheduling agreement numberTest Run: (deselected)

Choose .

A line with ERS-Pstable=X is displayed, referencing the schedulingagreement, the item 10, and the external delivery reference.

2. Write down the resulting invoice number. ______________________

a) Write down the invoice number (in the Document number column)._____________________

You can view the details of the invoice by clicking on the documentnumber.




Task 2: Display the invoice in SNCLog on as the supplier and display the invoice in SNC.

Hint: This task is performed in SNC. Since the invoice is related to theASN for the scheduling agreement release, you need to log on as supplierSNC100B-## using the user IU-SUPB##.

1. Log on as the supplier and display the invoice in SNC.

a) In the SNC supplier view, either navigate to the invoice from the ASNdetails screen (Invoices Related to ASN) or choose Invoice InvoiceOverview to find and display the invoice created.

Task 3: Conduct the payment runConduct the payment run.

Hint: This is again a task for the customer to be carried out in ERP withuser SNC100-##.


a) In the ERP system, choose Accounting Financial Accounting Accounts Payable Periodic Processing Payments or usetransaction code F110.

b) Make the following entries on the selection screen:Run date: Todays dateIdentification: ERS##

c) Go to the Parameters tab page and enter the following:Company code: 1000Pmt mthd: UNext p/date: today + 2 monthsVendor: SNC100B-##

d) On the Additional Log tab page, make the following entries:

Due check date:Pmnt method selection if not successful:Line items of the payment documents:Vendors (from): SCN100B-##Vendors (to): SCN100B-##




Due check date: selectPmnt method selection if not successful:selectLine items of the payment documents: selectVendors (from):SCN100B-##Vendors (to): SCN100B-##

e) On the Print/data medium tab page, make the following entries:

Enter the variant for the program RFFOAVIS_FPAYM: SNC100

f) Switch back to the Status tab page and save your entries.

g) Choose Payment run to execute the payment run, and confirm anywarning messages with Yes.

h) In the dialog box to schedule and start the payment run, make thefollowing entries:

Start date: todays date

Start immediately:

Create pmnt medium:

Choose Enter to start the payment run.

i) Choose Refresh repeatedly until the status is Posting orders: 1generated, 1 completed.

ResultThe payment information has been sent to SNC. You cancheck in transaction WE05 to ensure that an IDoc of the typeREMADV.PEXR2002 has been sent.


Hint: This finally is a task performed by supplier SNC100B-## (UserIU-SUPB##) in SAP SNC.

1. Check the status of the invoice in SNC

a) Log on to SNC as the supplier (IU-SUPB##) and choose InvoiceInvoice Overview. Choose Go to display your invoices. Your invoiceshould now have the status Paid.

b) Click the invoice number to branch to the Invoice Details screen. Onthe Payment status tab page, you can see the date and amount of thecustomer payment.



Lesson Summary

You should now be able to: Perform invoice collaboration in SAP SNC


SNC100 Lesson: Relevant Customizing for Invoice Collaboration in SAP SNC

Lesson: Relevant Customizing for Invoice Collaborationin SAP SNC

Lesson OverviewIn this lesson, you will learn about relevant Customizing for invoice collaborationin SAP SNC.


Customize invoice collaboration in SAP SNC Set up message determination for invoice collaboration

Business Example

Maintaining Tax CodesTo send calculated tax data between SAP SNC and the customers backend ERPsystem, you must maintain tax codes in both SAP SNC and SAP ERP. This isbecause SAP ERP uses the tax code to calculate the gross amount. Each tax codecan relate to a number of tax rates that you maintain.

Note: For more information about maintaining tax codes, see theImplementation Guide (IMG) for Supply Network Planning by choosingInvoice Maintain Tax Codes for Invoices.

Invoice NumberWhen you create an invoice, SAP SNC can automatically assign an invoicenumber.

For SAP SNC to assign numbers for invoices, you must have defined numberranges in the Web UI by choosing Master Data Number Ranges InvoiceNumber Range Intervals.

Hint: If you use an SAP back-end system, the numbers can have amaximum of 10 places. Therefore, limit the length of the order numbersin the number range attributes to 10 places.

To assign invoice attributes from the Web UI, choose Master Data NumberRanges Number Range Attributes.



Invoice Creation TypeIf you want the supplier to create invoices for purchase orders, you should beaware that there is a dependency between the invoice creation type and the GoodsReceipt-Based Invoice Verification indicator in the SAP ERP purchase order.

In the standard setting, the invoice creation type Invoice Creation with PurchaseOrder Reference is the default value for a purchase order or replenishment orderthat has been created without the Goods Receipt-Based Invoice Verificationindicator set. If the indicator is set, the invoice creation type will be set to InvoiceCreation with ASN Reference.

Message DeterminationMessage determination is relevant for creating IDocs in the ERP system. This isthe case for sending self-billing invoices and revaluation.

To send the IDoc for the self-billing invoice to the supplier you need to set upthe message determination in transaction NACE for Application MR, conditionrecordERS6. For this course we set up message determination based on the KeyCombination CoCode, Vendor.

Vendor Funct Partner Medium Date / Time Lan-guage

SNC100* LS sidCLNTxxx 6 4 EN

Partner ProfilesA partner profile controls which IDocs are created. You maintain partner profilesin transaction WE20; choose Tools ALE ALE Administration RuntimeSettings Partner Profiles.

Corresponding to the above entries in Message Determination, entries are requiredfor LS sidCLNTxxx and message type GSVERF (Basic type GSVERF03).


SNC100 Lesson: Relevant Customizing for Invoice Collaboration in SAP SNC

Lesson Summary

You should now be able to: Customize invoice collaboration in SAP SNC Set up message determination for invoice collaboration


Unit Summary SNC100

Unit SummaryYou should now be able to: Explain invoice collaboration within SAP SNC Perform invoice collaboration in SAP SNC Customize invoice collaboration in SAP SNC Set up message determination for invoice collaboration


snc100 6 invoice collaboration

Documents

sap snc snc100lesson

sap ag

sap sncsystem

sap netweaver tosap

invoice processing

sap sncstandard delivery

sap sncunit overviewin

selfbilling invoice