Improve Your Sales Order System in IS Standard Documents with airSlate SignNow

How to create outlook signature

[Music] hi friends welcome back to sap sd by manage tony this session will be dedicated for sales document type control here we'll discuss about the functionality of each and every field which we have in sales document type control so friends as a beginner before going to start sales document type control we have to understand what is the structure of sales document so each and every sales order comprises with header data item data and schedule line data header data will be controlled by sales document type item data will be controlled by item category and scheduling data will be controlled by schedule line category so in this session we'll discuss about header data controlled by sales document type so basically sales document type controls so first of all we have to understand what is header data header data of sales order will be controlled by sales document type it is the data which applies for all the line item in sales order so in sap sd we have different order to cast processes are there example inquiry quotation sales order russ order castle contracts conjunct process credit memo debit memo invoice correction requests and some other processes are there for different otc process order to cash process we have different sales document type in standard differentials document type will have a specific functionality different processes different transactions and different controls and that will be controlled by sales document types as we know each sales document type comprises with header data item data and schedule line data so here we'll discuss about the scheduling data so now i would like to give you some give you some examples of header data in sales order one example customer master and purchase order these are the fields comes under header data so now i'll go to the sap system i'll go to va01 sales order creation transaction code then i will show you what are the fields comes under header data sales document type ship to party purchase order number purchase date net value requested delivery date complete delivery required by law delivery block billing block payment terms incoterms one in cotton's two these are the fields comes under header data suppose example here sold to part is 25 sold to part is 25 then header data is applicable for all the line items suppose in sales order we are having two line item x and y for x and y customer is same so this customer is applicable for all the line item requested delivery date system determines requested delivery date 26 july 2022 this status will be same for all line item so header data will be applicable for all the line item now here structure i'll show you the structure these are the fields comes under header data header data these are the fields com center item data item data will be controlled by item category after sales document type control will go to the item category double click on line item then this is schedule line data so schedule and data basically consist deliver date and confirm quantity okay so today we'll discuss about the header data so one example is customer master po number these are the fields comes under header data and it is applicable for all the line item in that sales order so now we have to understand what is the source of header data first source of header data is customer master so how when we create sales order when you create sales order customer master is there and another one source when we create sales order system determines payment terms and in cotton 1 and cotton two example in cotton one in cotton two it's coming from customer master where we maintain payment term and in cotton we maintain in customer master sales area data billing tab so quickly i'll go to the customer master transaction code xd02 then we have to go to the sales area data under sales era data building tab we have in cotton one in cotton two and terms of payment now i'll change suppose i will maintain cif in cotton to vaporizer and suppose term supplement is triple zero five then these data will be copied from customer master to sales order so now create one sales order va01 25 so system determines from customer master so one source of header data is customer master another source is control data so control data is nothing but sales document type so we'll discuss sales document type today but for your knowledge i'll show you how it will determine from sales document so here you can see purchase order number and requested delivery number determined automatically so here we have to understand where system determines pure debt and requested delivery date from higher so quickly i will go to the sales document type control vob 8 transaction code to go for sale stock my type control is vov8 then i will go to the sales document type or double click on line item then scroll down so here i have checked propose pure debt and propose delivery date that is the reason system determines requested delivery date and purchase date into sales order from [Music] sales document type control so one source is control data now if i'll uncheck purchase order date and requested delivery date then system will not determine delivery date and pure debt automatically into the sales order now create sales order now pure debt and requested delivery that is blank because i have uncharged unchecked in sales document type control so if i'll check then only system will determine these date from the control data save now once again you will create then pure date and request delivery that will determine will be determined so now it's determined so another source of header data is control data control data and another one is configuration data so configuration data it will go to sales order enter the customer number then here sales area system consider sales area we have entered it manually while creating sales order but system consider this because in back end we are having configuration in enterprise structure if you don't have configuration then when you will enter the sales area sensor is nothing but sensor instance plus distribution channel and division system will give error message so this is the configuration data so now system determines pricing procedure from where based on configuration charging processor determination or bkk we have assigned this pricing procedure with combination sales area document pricing procedure and customer pricing browser interview questions what is the source of header data source of header data is customer master control data and configuration data so next header data so here we have to remember the process what are the standard process we have what are the standard sales document type and in real time which sales document type we use and what is the transaction code for it so first process is inquiry so standard sales document type for inquiry is in and in real time project will not use the standard sales document type for the transaction we have to create our own sales document type so generally we create the sales document types starting from z so in real time project we have to create zin a copy from standard sales document type standard sales document type is in newly created sales document type is jdin and transaction code to create inquiry is va11 second process quotation sales document type or standard sales document type for quotations qt in real time project will create jqt a copy from qt and transaction code is va 21 so here we have to remember in real time project we are not will not use the standard sales document type we have to create a new sales document type copy from standard sales document type you can start with z or we can start with why why because if anyone see that sales document type then he or she can understand that this is not the standard sense document type it is newly created sales document type g means customize okay so standard sales order or new sales document type zwr transaction code to create or is v801 standard sales document type arrow new sales document type zro transaction code is v801 next process is castle just document type standard cs new sales document type jcs transaction code is b801 return sales order sales document type re new sales document type jre transaction code is v801 credit memory quest cr new sales document type jcr transaction code is va01 then debit memo standard sales document type br initials document type zdr va01 invoice correction request rk zrk transaction code v801 free of charge sales document type fd new sales document type zfd transaction code v801 subsequent delivery free of charge sdf new sales document type ztf va01 consignment field of cf zcf va01 conjunct fill of ci jci transform code is v801 so here we have to remember the process standard sales document type and what is the transaction code to execute the absence document type next is conjunction written standard sales document type conr we have to create joanr this is a new sales document type transaction code v801 conjunction process standardized cp you can create jcp transaction code v801 scheduling agreement standard hds will create zds transition code to execute scheduling agreement each va 31 quantity contract qc new sales document type jqc transition code va 41 value contract channel wk1 new sales document type nucleated sales document type zwk1 transaction code is va41 value contract material specific standards document type zk2 real time jwk2 and transaction code is va41 these are the standard sales document type apart from this in real time project we use some special business processes like third party process individual purchase order process then make to order process stock transport order process asset sales scrap sales service sales service maintenance amc cnc then subcontracting demanding cell high c sales drop shipment so we are having some other standard business processes are there then path path and transition code to define sales document type path is spro sap reference spro sap reference img sales and distribution sales sales documents sales document header define sales document types and transaction code is vob-8 so now i'll go to the sap screen i'll show you the path path to go for sales document type control is spro click on sap reference img then go to sales and distribution go to sales and distribution then cells then sales document sales document header then define sales document type so i have already opened go back once again i'll go to the path quickly go to svro sap reference img sales and distribution sales sales document sales document header define sales document type okay so if we talk about the transaction code then transition code is vov8 v obviously the transaction code for sales document type control either you can go through the path or you can explore it by using the transaction code transaction code is v or v8 okay v obj8 so here i told that this is the standard sales order so we have to create our own sales document type so i'll show you how to create own sales document type so go to the transition code view va to go to position now ori the standard sales order now i have to create our own new sales document type select the sales document type standard sales document type click on copy as then i'll create zor because in real time project will not use the standard sales document type we have to create our own sales document type we have to copy from the standard sales document type enter then system will perform copy controls here so here click on yes then save it continue you can continue now save it it's already saved already saved it's a new sales document type created now we can use to create sales orders okay so now we understood how to create the new sales document type then go to sales document type double click on sales document type control then here first these are the fields which we have in sales document type control we have to understand the functionality of each and every field what is the uses of this field in real time project so it will take time i'll explain in details it will take time keep essence and go one by one so first field is sales document type control sales document type sorry sales document type called category what is the functionality of sales document category so we are having a document category having major role in sales document types so we are having various functionality of a particular field but it is first it will classify the sales document types then second it control the screen in sales order then delivery process which process is relevant for delivery which process is not relevant for delivery for which process directly we can create the delivery for which process we cannot create delivery directly with reference to that sales document type that will be controlled by document category next is order probability impact on order probability then track the document flow so here we are having five major functionality of document category we'll explain we'll we'll discuss one by one so first it will classify the sales document type whether it is inquiry quotation or standard sales order that will be classified by your sales document category so here you have to remember what is the document uh category for which sales document type for inquiry document category is a quotation b standard sales order russ order cell conjoint fill of conjunct issue containment pickup document category gc item proposal d scheduling agreement e all written standard return and conjointment return it is age all contract g all contract g quantity contract value contract general and value contact material specific that is g credit memo and inverse correction request k debit memo n free of charge and subsequent delivery free of charge that is i so first functionality is what document category will classify the sales document type so if you'll go to vob-8 if you'll explore this document category fields then you can see a for inquiry b for quotation c for sales order sales order means standard central roswell castle consignment issue consignment peak of consignment failure item proposal d scheduling agreement e all contracts it's all written i then sorry all return h i is what free of charge subsequent delivery free of charge credit memo inverse correction request k l e debit memo so c is for standard sales order so first it will classify the sales document type first point then second point controls it control the screen in sense order inquiry now i'll compare with inquiry and quotation inquiry and standard sales order for inquiry we are having validity period valid from and valid too but in standard sales order we don't have this field in standard sales order we don't have valid from and valid uh two so how system uh how system proposed valid from and valid to field in inquiry screen based on document category if document category a then only valid then valid format valid 2 will be there in inquiry screen so quickly i'll go to sap screen so go to inquiry in inquiry document categories a okay so i'll compare first we'll compare sales order screen and inquiry screen in sales order here you can see in sales order we don't have valid from and valid two fields but it will go to the inquiry then in inquiry then in inquiry we we have valid format value too so transaction code to create inquiries va11 sales document type is in so here we have valid form and valid 2. but in standard sales order we don't have valid from and valid to here you can see we don't have valid format valid too why because valid format valid 2 will be there if it is inquiry or quotation if document category is a or b but for standard sales order document category is c if document category is c then valid form and valid 2 will not be there if i'll change from c to a then in standard sales order itself we can get valid command value 2. now here you can see valid format value is not there go to va01 in standard sales order i can find valid from and valid too so in program we have this logic that if document category is a for inquiry or b for quotation or contracts then we have valid from and valid 2. if it is c then there is no valid form and valid 2. so this is one logic so it controls the screen in it control the screen in sales order so suppose here now we have compared with inquiry and quotation inquiry and sales order so inquiry if you go to the inquiry document categories a for a we have valid from and valid to quotation sd document category will be b for b also system will have system will have value from and valid too so transaction code to create quotation is va21 sales document type standard sales document type for quotation hqt so what i'll remove the reference mandatory again go to view 21 qt now here you can see we have valid from and valid too so for a document category a valid form is valid for b also valid 2 and valid from and value 2 is there if i'll change document category from b to c c is for sales order then again system will you will not find valid from and valid 2 for quotation if i change from b to c c means sales order okay so here you will not find valid form and valid 2 for quotation as well in backend we are having logic in program okay now here valid from and value 2 is not there so we are having control in sd document category it is b now we have compared with different different document category but if we'll talk about if we'll talk about wk1 and wk2 we have different screen here document category is same this is a contract so document category is g but screen is different wk1 you will find assortment module assortment module but here we don't have a software module we don't have assertment module document category is same but screen is different how how it will be controlled so first we will see the comparison of sales document so transaction code to create contract is va41 sales document type for value contract general wk1 so here you can see this screen is different here we are having target value and assortment module in wk1 in wk1 but if i go to the wk2 then you will not find the assortment module screen is different wk2 shell stock type w cato so here we don't have assortment module we are having material target value but wk1 we are having target value and assortment so where is the control for this okay so again so again this to go to sales document type wk1 for wk1 document categories g wk2 document category is also g then where is the control that system is proposing different screen so go to wk1 so document category now again document category is having relationship with screen sequence group field so if we have document category if two sales document types are there and document category is same then definitely we have screen sequence group will be different for wk1 screen sequence group is wk if you go to go to wk2 wk2 then screen sequence group will be different go to wk2 wk2 now screen sequence group is wk1 for wk1 screen sequence group is wk for wk2 sales document type screen sequence group is wk1 so screen sequence group is different for two sales document type so for wk1 wk1 [Music] assortment module is coming once again i'll create wk1 wk1 now our software module is coming and wk2 assortment module is not coming different screen so if i will change the screen here so wk2 if i'll go to the wk2 and if i'll change the screen sequence group from wk1 to wk then for wk2 also i'll get for wk2 also i'll get the assessment module so here we don't have assortment module now go to va01 wk2 here you will find the assortment model now screen is changed here you'll get this assortment module so now we came to know that document category will have relationship with screen sequence group if we'll change wk1 wky wk to wk1 then i'll not find the assortment module and i will get value contract material specific screen here you can see we don't have assortment module if i'll change screen sequence group from wk1 to wk then again i will get the assortment model assert model okay so it controls the screen in sales order then next delivery control delivery control means what if sd document category is c h or i then system will allow to create delivery for those sales document types suppose your document category for inquiry is document category for inquiry is a so with reference to inquiry directly i will not able to create the delivery we are having restriction in inquiry after inquiry i have to create the quotation with reference to quotation i have to create the sales order after sales order i can be able to create the delivery i will able to create the delivery because document category for sales order is c so system is telling that if document categories c or h or i then only i'll create the delivery with reference to that sales document type so here directly i unable to create the delivery for inquiry with reference to inquiry because here document category is a for quotation document category is b so with reference to quotation i will not able to create the delivery because document categories b after delivery i have to create sales order then with reference to sales order i have to create the delivery so i'll show you one scenario example or with reference to or i can create va01 z or i can able to create the delivery directly order saved i can able to get the delivery but if i'll go to inquiry go to inquiry i have created sales order and delivery for jwr document categories c once again you remember this logic if document category is c h or i then for those sales document type i'll create delivery with reference to that sales document type so c over document category c so i can able to create the delivery next scenario if document category is a or b then i cannot able to create the delivery directly now if you will go to inquiry in document category is a so create inquiry create inquiry transform code to create encourage va11 in seth then now create delivery now you cannot able to clear the delivery now delivery relevant item for this sorry now take va 12 i'll take the delivery number yes or inquiry number then i'll create delivery for this inquiry give the inquiry number enter the transaction cannot be delivered because document category is a if it is c or h or i then only i can able to create the delivery because here one point i i want to discuss with you wait first i'll change i'll change from a to c then for inquiry i can able to create delivery directly now i have changed from a to c now create a inquiry now create a inquiry bi11 inquiry save it then now create delivery now i can able to create the delivery because document category changed from a to c now i can able to create the delivery with reference to inquiry pgi now for your reference i want to show you the document flow go to change mode of the inquiry then click on document flow you will find inquiry there is no quotation no standard sales order directly delivery so system will allow to create the delivery if document category is c or h or what i so standard sales order or directly will create the delivery remember the standard process truss order delivery will be created automatically castle delivery will be created automatically conjunct issue then delivery containment return conr document category is age so with reference to cnr i can create delivery of charge free of charge ft charge fd i can create delivery subsequent delivery free of charge with reference to this i can create delivery but with reference to contract wk1 wk2 quantity contract inquiry quotation i cannot able to create delivery directly i have to go for sale sort of then delivery because st document category says that if document categories chi then only system will allow to create the delivery so i hope you understood what is delivery control what is the role of sd document category in delivery control next field is order probability so what is order probability order probability is what order probability is what is the percentage what is the chances to convert that sales document type to sales order suppose if any customer inquires about the product then what is the chances to convert this sales order user inquiry to sales order that is 30 as for the sap survey if we send the quotation to the customer then that quotation will be converted to sales order that is percentage is 70 percent so what is the converted to that inquiry to order that is the percentage order so order is already order converted so it is 100 percent so order probability field will be controlled by category so go to sales order be open go to sales order or or zwr zor then order probability field this field you can see this field is grayed out this field is grayed out if document category is c then probability field will be grayed out we cannot change this so if we'll go to the ppt then if sales document category is c then system will not allow to change the order probability in backend we are having logic in the program if document category is c then order probability field will be grayed out we cannot change it then next inquiry and quotation for inquiry and quotation we can change if i'll change the document category a if i'll change the document category a then this field can be changed if else if i change from a to c then again it will be grayed out again this field is great out i cannot change it so if it is c then we cannot change it if it is a or b then we can change so if you want to change then here you have to change from c to a or b then change then make it c again okay so i'll change from 80 percent to 100 percent okay if it is a then i can change b also i can change okay so i'll change from c says to c then quickly i'll go to the inquiry then document category is a and incorrectly a okay inquiry a then probability will be 30 and it can be changed then go to quotation qt it is 70 percent and it can be changed so order probability we have already discussed then track the document data so track the document data i mean document flow so we can track the data in document flow suppose now we have to understand what is preceding document preceding document means previous document suppose for billing for billing preceding document is delivery so this is billing document number inverse number then preceding documentation delivery then what is the preceding document for delivery receiving document means previous document of delivery sales order the previous document for delivery is preceding documentary sales order then what is the preceding document of sales order quotation for quotation preceding document is inquiry preceding document means previous document so now we'll talk about the preceding document we understood now you have to talk about the follow-on document follow-on document means next document for inquiry follow-on document is quotation for quotation follow-on document is sales order for sales order follow-on document is delivery for delivery following document is invoice so these are the document category so for inquiry document categories a quotation document category is b sales order document categories c which we have already discussed now i will show you what is the document category for delivery so now we have to go to the delivery type control transaction code for delivery type control is ovlp it will go to lf then document category is j this is not p that is j okay this is not t j t is for return delete this is j okay j so this is the document category if you go to the billing type transaction code to go for billing type control hbofa so document category for standard billing type is f2 and document category is m document categories m this is a very important point which we have to understand so now i hope we clear what is preceding document and follow-on document suppose your client your core user your end user will give the sales order number and will ask to provide the delivery number then i will get this document flow document number by using table so table is vb documentable document flow table okay so now i'll go to the ac 69 so i'll open this sheet okay suppose your user given the sales billing document number billing document number now they are asking for delivery number delivery number so go to sc n sc 16 n then table for document flow is vba please remember table for document flow is vba so now you tell me this is preceding document or follow-on document this is follow-on document i have to get the preceding document number preceding means previous document number follow-on means next document number okay so here i have to pass the following document number follow on document with next then you can deselect all select in follow-on document number and preceding document number so here i have to know preceding document number here we have to pass the following document number then we have to take select receiving document then we have to pass preceding document category so here we are having two document category here four things we have to understand what is what are those first is preceding document then for loan document so as i told that follow on document means previous document sorry follow on document means next document or last document preceding document means previous document so i know billing document number so follow on document number i know i have to know preceding document so here you have to pass preceding document category preceding document category so delivery document category so delivery document category is j if i pass j then sorry here document category document category if i pass j over here then i will get delivery number i'll get the delivery number sorry sorry i have to pass this in preceding proceeding i need previous document so again once again suppose i i know i know follow on document i want to get preceding document then here you have to pass preceding document category so for delivery preceding document categories j so here i have to pass the j j then execute this is the delivery number this is the delivery number okay so follow on document now suppose i know delivery number i want to know the billing document number how to get it once i can go to ac 69 sc 69 for professor it may be a bit confusion but try to understand okay so now i know the preceding document so here you have to pass the preceding document here you have to pass the preceding document deselect all what are the required field you check then i know the following document right now so here you have to pass the subsequent document category for billing subsequent document category each aim for billing subsequent document categories m so here you have to pass m subsequently categories m then i will get then i will get then i'll get this adds my billing document execute this number is 900 39809 [Music] you'll get it okay so now i know the delivery number i want to the i want to know the order number i'll go in a sequence so if you are having entries then you can delete all entries here okay so here what you know delivery number delivery number is follow on document number this is following document number i know preceding document so here i have to pass the preceding document category what is the document category for sales order c this is your sales order number then next i know order number i want to know quotation number so here following document is sales order i have to know quotation we'll start from sc 16 n or else if you are new then you will be confused so right now i know order i want to know the quotation number so follow-on document is sales order i have to take i have to take preceding document and preceding document category for quotation is b execute so this is your quotation number here two line are coming because here we are having two line item two line item are there in that quotation so it is coming too okay then now this is following document number now this is following document number i have to know inquiry number so pass the following document number path the following document number i have to know the inquiry number in preceding document category i have to pass the document category for which we want to know so precision document category document category inquiry so document category for inquiries a then i'll get the inquiry number this is inquiry number because i am getting two because i am having two line item in that sales setup so you might have a question why we are using why we are using why we are using these table to get inquiry quotation sales order delivery invoice if we'll go to the change mode of the quotation or inquiry then we can get the document flow you can go to document flow then you'll get the inquiry document so this is inquiry number will match in card number is this quotation number is this sales order number is two zero two one zero this is your delivery number and last one is your billing document number so why we are using this table if you can get inquiry quotation sales order delivery in document flow suppose if it is one entries then you can get it through document flow but if your client given 5000 entries then how will get this that is the important point suppose your client your client will give 5000 sales order and he will ask to provide the delivery number for this invoice what is the delivery of what are the delivery number sales order number quotation number and inquiry number so how to do this for numbers of sensors then again go to sc 69 sc 69 bbf dbfa now we know now we know now we know the preceding follow-on document so click on this arrow mark then click on upload from clickboard you have to copy all the invoice you copy from here copy then paste here then execute then execute so i have to know delivery number so preceding item if i'll pass 10 then i'll get 1 1 entries okay so these are the delivery number or sorry sorry sorry sorry sorry i have not checked the preceding document field so these are the delivery number at a time i can get all delivery numbers same way it will copy it will copy delivery number then if you want to get the sales order number then go to sc 69 sc 69 then pass the follow-on document click on clipboard execute see check receiving document and pass the preceding document category receiving document category c search for sales order okay these are the sales order in this way we can get it and we use the sales document number okay we use the sales document number sorry sales document category okay so now we got some information about document category then go to sales document type control next field is what i'll go to sales order or or zwr next field is sales document block so what is sales document block sales document block determines whether the document is blocked for use so in in real time which when will use this sales document block process is not used suppose uh we used initially we have implemented a demanding sales process for a demanding sales process and right now this process is not in use so the client requirement is what for demanding cell suppose sales document type is zord ztrd and client requirement is now this process is not in use users not system should not allow to create sales document for that sales document type then we have to use sales document block so in real time if any process is not in huge then we block that same stock type temporary sales document type temporary sales document type means if you can talk about the trade sales trade sales means trade fair suppose trade fair is going on for a week so for that trade sales trade pair we are selling the product to the customer and for reporting purpose and for reporting purpose we use a new sales document type and we use that sales document type for that trade pair only thereafter will not you with that thereafter will block for this so why we use this why we use a sales document type temporary for a particular purpose for reporting purpose then next is block for a period due to some reason we don't want to use that sales document type for a month for a period then we can plot this if any sales document is blocked then when user will create sales order system will not allow to create sales order for that sales document type it will be blocked so now here i'll maintain block sales document type block suppose element and x save it then system not allow to create sales order for zor sales document type now create sales order slash and va01 jdor now system is giving message what is the message sales order type jdo are blocked for processing we cannot create sales order for this sales document type so if any document is blocked if you uh if we check blocked in cell document type then system will not allow to create sales document type sales sales order for that document type so recently we have in last project we have used this block so trade off here was there for trade fair they used ztr diesel's document type so they used for a period temporarily starting from this state to this state after this death system should not allow to create sales order for jtrd because this is temporary sales document type generally why in real time project why they are using a separate sales document type for trade cells or any specific sales document type for reporting purpose so now i'll show you i'd create one sales order for jtrt jtrd x material enter save so if you want to generate the report so standard transaction code to generate the sales report is ba05 or va05n now i want to get the all sales order i'll pass the sales document type suppose it says document type drd so here you can see how many sales order we have created what are the document number what is the document though uh document number what is the document date material number here we'll get the purchase order number sales organization distribution channel division sales office sales group and how many how much how much revenue we have generated for this sales order sales document type in trade sales we can get everything i will execute that here we are having the report so if management will ask to provide the sales report for trade sales what was the sales revenue for trade sales then we'll pass the sales document type in va05n and we'll get all the information so sales order number description then sold to party created on document date created by whom what is the sales area for that what is the document currency and what was the net value so i have created one if i'll create another one sales order then that health order will be captured in this report so now this is second sales order number second cell photo i am creating with this chance document type x material then i'll take i'll take two material okay y material save this if document is incomplete then also notice to save it then now generate the report i will get two sales order with document type trade cell that is jrtrd execute okay so two sales document type for reporting purpose so who you jt are the after 15th of july 2022 we have blocked this now i'll block jtrd sales document type click on this next mark then ztrd enter now i'll maintain the block then system will not allow to create sales order for this document type okay so now create a sales order pa01 enter now system will not allow to create for sales order for this sales document type so so next field is indicator so next field is indicator okay so we use indicator only for sales document type rk which is invoice correction request so what is the functionality of indicator each line item from invoice will be copied as two line item in so so precondition to learn indicator is what we have to know the process of invoice correction request so we maintain indicator as d for inverse correction request so we'll test this what is the functionality of indicator so transition code to create inverse correction request is sorry to create inverse correction request va 0 1 sales document type is rk then enter so inverse correction request will be created with reference to invoice so billing document i have already created okay so copy then each line item from inverse will be copied as two line item so if we'll remove the indicator then two line item will not be there remove indicator again va01 inverse question request rk with reference to invoice so here each line item will not copy that 2 line item so indicator d will copy each line item from invoice as to line item in inverse correction request order now two line item first is credit and second line is debit so debit line can be changed credit line first line will be displayed mode grayed out we cannot change anything so for that i'll explain to real-time scenarios first we have to understand what is invoice correction request when user do any mistake in invoice we correct invoice by using the process invoice correction request based on user mistake we can deduct the amount from the customer outstanding so inverse correction request process is inverse correction request sales order there is no delivery because here we just correct the invoice so scenarios in real time scenarios about the inverse correction request if quantity difference price difference or we can raise credit memo by using invoice correction request now we'll talk about the real time scenarios then you will understand about the invoice correction request and indicator so first scenario this is first real time scenarios so inverse quantity 10 build quantity 10 and in that build quantity two quantities damaged totally damaged so if quantities are totally damaged then generally we will not take that goods from the customer location to plant location because if we'll take this goods from the customer location to plant location unnecessarily we have to pay the shipping charges to the transporter because who are totally damaged these are not these two goods are not in repairable condition so will not take that goods into the plant so first is credit line so in credit line we have in original inverse our quantity is 10 our quantities are 10 each quantity 10 1000 so 10 000 10 quantity into 1000 total inverse value is 10 000 but in debit line we have to make it eight because two quantity has damage we have to refund the amount of two quantities so we have to charge 8000 against that inverse and 2000 will be refunded so this is quantity difference first in average quantity difference so here first inner quantity difference here i have to change it then in net value i will get 2000 amount which amount i have to refund to the customer so i have to charge eight quantity and 2000 will be refunded 2000 will be refunded sales okay so we have to give order region so damaging transit save it no delivery there is no physical movements of goods directly create invoice vf01 enter then save it save it then another one real time scenarios is quantity difference second one is price difference so in original inverse we have built one thousand per quantity and we have delivered the goods to the customer but customer not agreed to take the goods for 1000 for quantity customer is customer will pay 800. so negotiation price negotiation price is 800. so 200 poor quantity for each quantity we have to refund 200 into 10 means 2000 so this is 8 this is not 80 this is 8 okay so 10 sorry sorry sorry sorry it will be 10 this will be also 10 there is no changes in quantities so we have charge 1000 here we have to charge eight thousand per quantity 800 so again here we have to refund two thousand quantity two thousand amount to the customer so here we have to change the price you can create inverse correction request ea 0 1 rk then i have already created few invoices for testing purpose copy copy then now there is no difference in quantities there is no changes in quantity there is changes in pricing so double click on second line item which is debit line then go to the condition here you have to change your base price from 1000 to 800 enter then go back so here again we have to refund 2000 amount to the customer save it oh sorry give the order region price discrepancy give some region save it then create invoice pf01 so this is debit memo save okay so next interview question what we have covered yet what is the purpose of sd document category purpose of sd document categories it will classify the document type it controls screen in sales order track document data track the document flow having changes in order probability order probability if document category c then order probability field will be grayed out if it is a or b then we can change it then next is delivery process if document category is c or i or h then we can create delivery for those document type directly if document category is not c or i or h then we cannot create delivery directly example inquiry document category is a so with reference to inquiry if document category is a then directly you cannot create delivery inquiry then quotation or inquiry then sales order when query then quotation then sell server then delivery so what is sales document category for all sales document type inquiry a inquiry a inquiry a quotation b order parasol castle consignment fill up conjunct issue container pick up d shield line agreement e return consignment return age all contracts g credit memo and inverse correction request k debit memo l free of charge subsequent delivery of charge i what is st document block if you block a document if you block a sales document type user cannot create a sales document for this sales document type then what is indicator indicator d control that each line item from inverse will be copied as two line item in invoice correction request next question for which sales document type we use indicator only invoice correction request okay so guys if you have any questions then you can [Music] directly call to me or text me so that i'll try to resolve that issues i'll try to clarify your doubts so guys if you have not yet subscribed our channel then please subscribe our channel to get a notification to subscribe our channel and click on bell icon to get notification for upcoming sessions so guys thank you so much for watching this session