Inbound shipment for tracking of vendor del mat & payment of service agents
HI,
Experteese,
we are going to implement transportation mgmt and exclusively for inbound shipment can any body give the details of inbound shipment and how to settle the payments to the service vendors
is there any approval process apartfrom po, against inbound delivery or shipment. My client will pay the payment on bill of lading.basis.
plz let me know how to go
Thanks
RAO
PO with frieght cdn type emplty ( caarry out shipemnt cost in cdn type)
vl31n for PGR
Vl01n - shipment cost doc with route determination if necessary ( u can maintain cost at header or for each stage of route)
vi01 for shipment cost calculation.( frieght charges + services)
Miro for PO vendor.
REgWARDS
Similar Messages
-
Use shipments for track and trace
I'm investigating the option of using Shipments for Track & Trace.
The process that we would like to cover is as follows:
1. (web) order is created by customer. The goods will be collected in our shop.
2. STO is created, based on SO. supplying site/plant is our DC, receiving site / plant is our shop
3. The DC post goods issue (for outbound delivery)
4. The goods are picked up by our carrier
5. The goods arrive at our carriers warehouse
6. The goods are issued from our carriers warehouse
7. Our shop receives the goods (Goods Receipt on STO)
We would like to monitor step 4, 5 and 6
We thought of creating a shipment for the delivery and either use the Deadlines or Stages.
I would like to get some advice about what is the best solution.Hi,
As far as my knowledge, the functionality of tracking and tracing the vehicle in a shipment is not possible in ERP.
You may want to explore the use of Transportation Management (TM8.0) for this purpose.
Thanks. -
UserExit or Customer Exit for F110 - '*' on Vendor Line Item Payment Run
Dear all,
Background
Currently in F110, when processing for vendor payments, the item text ( or segment text) is only printed out when item text begins with an asterik ' * '. The asterik is meant to indicate that this document/item is posted from external system. You may do a F1 on the text field for detail explanation.
In the event, asterik is not present on the item text even if the text is not blank, it will not be printed at all.
Here are two OSS notes on the asteriks: 312623 and 1292333.
Include: F110SFS0_SATZ_KOMPLETTIEREN
*------- Segementtext
IF REGUP-SGTXT(1) NE '*'.
REGUP-SGTXT = SPACE.
ENDIF.
Requirement
User is requesting for item text to be printed at all time, when the text exist, regardless of ' * '.
Question
Does anyone know of a user exit / customer exit that i could use to do modification for SGTXT ?
Would appreciate it, if you could share your suggestions / experiences - on this matter, even if it doesn't need to be resolved through user exits. Thanks in advanceBTW..you have fot following exits for F110;
Transaction Code - F110 Parameters for Automatic Payment
Enhancement/ Business Add-in Description
Enhancement
RFFOX074 Frame for user exit RFFOX074 (in program RFFOCH_U)
RFFOX075 Frame for user exit RFFOX075 (in program RFFOCH_U)
RFFOX081 Frame for user exit RFFOX081 (in program RFFOF__T)
RFFOX082 Frame for user exit RFFOX082 (in program RFFOF__T)
RFFOX100 Frame for user exit RFFOX100 (in program RFFOUS_T)
RFFOX101 Frame for user exit RFFOX101 (in program RFFOUS_T)
RFFOX102 Frame for user exit RFFOX102 (in program RFFOUS_T)
RFFOX103 Frame for user exit RFFOX103 (in program RFFOUS_T)
RFFOX104 user exit
RFFOX105 Frame for user exit RFFOX105 (in program RFFOUS_T)
RFFOX200 Frame for user exit RFFOX200 (in program RFFONZ_T)
RFFOX210 Frame for user exit RFFOX210 (in program RFFOAU_T)
RFFOX211 Frame for user exit RFFOX211 (in program RFFONZ_T)
RFFOX230 General program for user exit RFFOX230 (in program RFFOJP_L)
RFFOX240 Enhancement for User Exit 240 (RFFOAT_P)
RFFOX250 Enhancement for User Exit 250 (RFFODK_E)
RFFOX901 Framework for user exit RFFOX901 (in program RFFOM100)
RFFOX902 Framework for user exit RFFOX902 (in program RFFOM100)
FDTAX001 Enhancement to Transaction FDTA (event after the download)
FEDI0002 Function exits for EDI DOCS in FI - Incoming pyt adv.notes
FEDI0003 Function exits for EDI docs in FI - Save PEXR segments
FEDI0004 Function exits for EDI docs in FI - particular events
FEDI0006 Function Exits for EDI-docs in FI: Save IDCR Segments
RFFOX003 Frame for user exit RFFOX003 (in program RFFOM100)
RFFOX041 Framework for user exit RFFOX041 (in program RFFOBE_I)
RFFOX042 Framework for user exit RFFOX042 (in program RFFOBE_E)
RFFOX043 Framework for user exit RFFOX043 (in program RFFOBE_D)
RFFOX061 Frame for user exit RFFOX061 (in program RFFOCH_P)
RFFOX062 Frame for user exit RFFOX062 (in program RFFOCH_P)
RFFOX063 Frame for user exit RFFOX063 (in program RFFOCH_P)
RFFOX064 Frame for user exit RFFOX064 (in program RFFOCH_P)
RFFOX065 Frame for user exit RFFOX065 (in program RFFOCH_P)
RFFOX066 Frame for user exit RFFOX066 (in program RFFOCH_P)
RFFOX071 Frame for user exit RFFOX071 (in program RFFOCH_U)
RFFOX072 Frame for user exit RFFOX072 (in program RFFOCH_U)
RFFOX073 Frame for user exit RFFOX073 (in program RFFOCH_U)
Business Add-in
FI_BSTM_MC_EXIT FI Account Statement: Exit from MultiCash Conversion
FI_F110_SCHEDULE_JOB F110: Check before scheduling a proposal/update run -
Can i give multiple versions in purchase inforecord for same vendor and mat
can i give multiple versions in purchase info record for same vendor and mat code..is is possible??? plz help me
thanks and regards
Ramesh Reddy(VALLUR)HI,
No .where you are getting version in purchasing info record ? why you want version ? suppose we put version then where you used that version ?
to get clear picture regarding purchasing info record
check following link
[http://help.sap.com/saphelp_46c/helpdata/en/75/ee102f55c811d189900000e8322d00/content.htm]
Regards
Kailas Ugale -
GR to be done against only Inbound delivery for selected vendors
GR to be done against only Inbound delivery for selected vendors. If the user putsthe combination " Goods Receipt+ Purchase Order+ Purchase Order Number " in MIGO , the error should be displayed as "Create MIGO with Ref to ASN"
At the time of MIGO, when user put the combination of Goods Receipt+ Purchase Order and purchase order number, BADI will activate.
BADI will search the vendor code from the entered purchase order in the Z table in which user maintain the vendor codes.
If BADI finds the vendor code in the Z table then, will give error as u201CPlease create inbound delivery firstu201D.
If BADI does not find the vendor code in Z table then it will inactive.
In short we are restricting the selected vendor for MIGO with reference to PO.Hi,
If u had used confirmation control key (0001) - In Item details of PO, as per standard SAP u cannot proceed for GR without inbound delivery. Otherwise use MB_MIGO_BADI. Thanking you -
For inbound Shipment IDOC ' IDOC_INPUT_SHIPPL' does not populated the stop
hi ,
I am using an inbound IDOC for shipment IDOC_INPUT_SHIPPL' .
and I am sending the Stop time in the segment E1EDT17 with qualif = 011 and ISDD,ISDZ,IEDD & IEDZ. and with diferent location say E1TPTRM has 2 differnet location 1) Plant location 2) Ship to address
in my IDOC there are date , time ie planned date * time but in SAP VT03n transaction it is not getting updated in the screen in the Stages tab.
is there any specific condition i need to send in the file. please helpHI
I got the answer for it.
This has to be delt in the E1EDP02 segment with the qualifier value as 083 and the document value as the plant
Thanks
Nikhil -
What are the T-codes that contain the master data for material and vendor?
what are the T-codes that contain the master data for material and vendor?
hi ,
- Display Material tcodes...
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
for vendor..
XKN1 Display Number Ranges (Vendor)
XK01 Create vendor (centrally)
XK02 Change vendor (centrally)
XK03 Display vendor (centrally)
XK04 Vendor Changes (Centrally)
XK05 Block Vendor (Centrally)
XK06 Mark vendor for deletion (centrally
XK07 Change vendor account group
XK11 Create Condition
XK12 Change Condition
XK13 Display Condition
XK14 Create with cond. ref. (cond. list)
XK15 Create Conditions (background job)
reward points if useful,
venkat. -
Inbound Shipment and Leg creation
Hi All,
We are manually creating legs (stages) in Inbound shipments in 3 party scenario, its a direct leg from vendor to customer. During leg creation process i am able to give the Vendor (departure details) including points, shipping point and vendor as it is defined in the Inbound delivery partner tab under vendor. But while trying to get the data for customer im not able to pull the customer details for destination address. points and customer details.
The customer ship to party has been maintained in sales order header level in partner tab, but do i need to maintain it in the inbound delivery partner tab under buyer head.
Or is it like every time i need to fill in the details manually from the sales order SH address (this will make process tedious and time consuming)
Let me know how can i find the customer details in the destination address of create leg in shipments.
Thankshi ,
What was the solution for this, since i am getting the same error.
Please help.
Thanks,
Mauryan -
hi,
following is my client's requirements in third party processing...
normally we have customers in different parts of india, and we get third party orders from different customers. and we raise one single PO to vendor located in china. and he couriered the goods to Hong kong to chennai port. the container have different sales ordered goods.. from chennai it is moving to different parts of our indian customer's site. this is the scenario.
As per MM concern , I have to configure.
1.P O
2. Order Acknoledgement
3. delivery Confirmations through different inbound deliveries
4.Inbound shipment from Hong konh to Chennai and Chennai to mumbai, Chennai to delhi, Chennai to hyderabad..etc
5. calculate inbound shipment cost,
6. Enter migo. with respect to ____
how to map this scenario?? especially Routes and inbound shipment
regards
rajHi,
As per MM concern , I have to configure.
1.P O
2. Order Acknoledgement
3. delivery Confirmations through different inbound deliveries
4.Inbound shipment from Hong konh to Chennai and Chennai to mumbai, Chennai to delhi, Chennai to hyderabad..etc
5. calculate inbound shipment cost,
6. Enter migo. with respect to ____
You can map the process as
P.O (ME21N) >>> Order acknow >>> Create inbound delivery(VL10B) >>> Create Inbound shipment document (VT01N)>>> Create shipment cost document(VI01) >>> MIGO / Post goods reciepts from delivery itself (VL02N)
For this requirements are as
Define Routes & transportation zones
Maintain transportation relevance for Delivery types & delivery items & routes
IMG >> Logistic execution >> Transportation >> shipments >> maintain trans relevance.
Kapil -
Tables for vendor invoice and payment
Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation -
Inbound Delivery For Scheduling Agreement Lines using LSMW
Hi,
We need to create inbound deliveries for scheduling agreements. Our scheduling Agreements are too big with 200 lines. But the vendor used to send only few discrete lines in his ASN. Is it possible to create inbound deliveries for the Scheduling agreement using LSMW? Is there any standard BAPI or IDOC available to handle this in LSMW? Has anyone done this before?
Our requirement is as follows.
1. Create Inbound Delivery for few lines of the Scheduling Agreement
2. The delivery quantity of the inbound delivery will be a partial quantity of the Scheduling Agreement
3. Materials are batch managed and the batch number for each inbound delivery item need to be captured.
4. Vendor's ASN Number and its item number need to be captured at inbound delivery header and item level respectively.
Note: Delivery Schedule of the Scheduling Agreement is not used in the above scenario.
If you have any input, it will be really appreciated.
Regards,
SP0526Hi,
You can give your scheduling agreement number in the field Purchase Order.
If you want select from the list, you can click on PO tree (just under create inbound delivery). There selet document category as "L". You will get the scheduling agreement list.
Regards,
Prabu -
Goods receipt through Inbound delivery for Sub-Contracting Purchase order
Hi
I am trying to do goods receipt for the inbound delivery /shipping notification created for a sub -contracting Purchase order. The Finished product and the component part are batch managed, When I try to perform PGR in VL32N , I am getting a blank screen as error message and Goods receipt is not getting triggered . I checked for OSS note and found 645119 close to my issue but not an exact match . We are in ECC 6.0 with EHP 4. Can some one clarify whether it is possible to post GR through inbound delivery for a Subcon Purchase order .
Thanks in advance for your immediate response.
with regards,
Joseph Anand BHi, The issue may be due to this - the component is batch managed but the batch data is blank in the component list of the Purchase Order Item. Or a batch is maintained in the PO item component list but the stock for the same batch is not available with Vendor, i.e. stock with some other batch may be available.
In a receipt for Sub-cont PO, 101 happens for FG and 543 happens for component. But there is no option to provide the component details in a delivery. So in standard system, when 101 happens via a delivery, 543 will be posted in the background. So any error in posting 543 will result in a blank screen without any error message.
You can fix this by maintaining correct batch in the PO component list.
But there is another issue - you cannot do 'cancel posting' and 'return delivery' for this receipt. Only you can reverse the inbound delivery and you should know that the recevied stock shouldn't have been processed to do reversal of inbound delivery. -
hi,
For our Scenario., schedule line is generated from scheduling agreement with vendor.
And, Shipment for schedule line is created successfully, using VSR Optimization.
and in OLTP Generation of deliveries, I am getting List with my shipment for which the deliveries to be generated in ECC.
but while executing, I am not getting any error (except application log in /SAPAPO/C3) as well as no delivery created in ECC which stopping me for "check Release of planned shipment. " and move the shipment to ECC
Could anyone suggest me how to process the shipment for schedule line (based on scheduling agreement)
Regards
Maran
Edited by: DP.Maran on Mar 7, 2010 11:33 AMDelivery generation was blocked in ECC, cahnged teh confirmation control key in shceduling agreement (0036)
this allowed me to generate Delviery in ECC -
Inbound Logistics: ASN, Inbound Deliveries & Inbound Shipments
We are attempting to implement an inbound logistics process. Inbound delivery and inbound shipment configuration is NOT an issue, but our internal business partners are concerned about the accuracy of the vendors shipping operations and does not trust that they will send an accurate ASN (qty, u of m) to us to generate the inbound delivery. Does anybody have any experience and success in using a method other than ASN to automatically generate the inbound delivery, such as generating it at goods receipt, etc?
You should meet with your supplier and make sure they understand the importance of timely and accurate information in relation to your future business relationship. If necessary, remind them that there are other suppliers in the market.
Then, after they have started to provide ASN data, meet regularly to review adherence to schedule and remedial actions. Their performance should be included in the annual pricing negotiations.
Good luck,
Dave -
"Inbound deliveries for PO reciepts with confirmation control keys"
Hi Gurus,
Can somebody tell me the detailed configuaration steps " Inbound deliveries for PO reciepts with confirmation control keys".
Thanks
RajHi,
Del. type is identified in
OLME-Confirmations-Define Internal Confirmation Categories
Del. item catogery is defined in TCode 0184.
Based on Del. type & item cat. grp in Material master
Goods Recieving point (shipping point) against Plant & SLOC is defined in
Logistics Execution-Shipping-Basic Shipping Functions-Shipping Point and Goods Receiving Point Determination-Assign Goods Receiving Points for Inbound Deliveries
Maybe you are looking for
-
I have a iPhone 4 and lately it has been shutting down randomly when I still have battery left. It also doesn't turn back on, until I plug it in to the charger. But when I plug it in, the low battery sign shows up then comes to the lock screen with l
-
Should I be entitled to Home Hub 4
Hi all, I joined BT from Virgin Media after June 1st. I am on the unlimited 2 package but was fitted with a Home hub 3 which has consistently failed to work since fitted. After 3 complaints it is finally being changed to.....another home hub 3. As I
-
Is there a way to know when a gif animation ends to switch to a new image?
Okay so basically I want to apply somt effects to my image that I was going to create in photoshop. I was just changing it from orange/red to a more deeper red. I figured I would set the first picture, then the gif, then the second picture. Or is the
-
Hi Gurus, In DP can i use standard KF(9AFCST...etc) and CHAR for my configuration ? Please let me know Thanks for your answers Raj
-
Error installing Apps on my Z10 from BB World
I've just recently started to get an error message on my Z10 when downloading apps that say "Error Installing Application" with a red bar. I thought it may have been the app I was originally trying to download, but I tried others and I continued to g